Module aws_sdk_glue::types
source · Expand description
Data structures used by operation inputs/outputs.
Modules
- Builders
- Error types that AWS Glue can respond with.
Structs
Defines an action to be initiated by a trigger.
Specifies a transform that groups rows by chosen fields and computes the aggregated value by specified function.
Specifies the set of parameters needed to perform aggregation in the aggregate transform.
Specifies an optional value when connecting to the Redshift cluster.
Specifies an Amazon Redshift node.
Specifies an Amazon Redshift source.
Specifies an Amazon Redshift target.
Specifies a transform that maps data property keys in the data source to data property keys in the data target. You can rename keys, modify the data types for keys, and choose which keys to drop from the dataset.
Specifies a connector to an Amazon Athena data source.
A structure containing the Lake Formation audit context.
A list of errors that can occur when registering partition indexes for an existing table.
Specifies a target that uses a Glue Data Catalog table.
Records an error that occurred when attempting to stop a specified job run.
Records a successful request to stop a specified
JobRun.Contains information about a batch update partition error.
A structure that contains the values and structure used to update a partition.
Defines column statistics supported for bit sequence data values.
The details of a blueprint.
The details of a blueprint.
The details of a blueprint run.
Defines column statistics supported for Boolean data columns.
Specifies a Delta Lake data source that is registered in the Glue Data Catalog.
Specifies a table definition in the Glue Data Catalog.
Specifies a Hudi data source that is registered in the Glue Data Catalog.
A structure containing migration status information.
Specifies an Apache Kafka data store in the Data Catalog.
Specifies a Kinesis data source in the Glue Data Catalog.
A policy that specifies update behavior for the crawler.
Specifies a data store in the Glue Data Catalog.
Specifies an Glue Data Catalog target.
Classifiers are triggered during a crawl task. A classifier checks whether a given file is in a format it can handle. If it is, the classifier creates a schema in the form of a
StructTypeobject that matches that data format.Specifies how Amazon CloudWatch data should be encrypted.
CodeGenConfigurationNodeenumerates all valid Node types. One and only one of its member variables can be populated.Represents a directional edge in a directed acyclic graph (DAG).
Represents a node in a directed acyclic graph (DAG)
An argument or property of a node.
A column in a
Table.Encapsulates a column name that failed and the reason for failure.
A structure containing the column name and column importance score for a column.
A filter that uses both column-level and row-level filtering.
Represents the generated column-level statistics for a table or partition.
Contains the individual types of column statistics data. Only one data object should be set and indicated by the
Typeattribute.Encapsulates a
ColumnStatisticsobject that failed and the reason for failure.Defines a condition under which a trigger fires.
The confusion matrix shows you what your transform is predicting accurately and what types of errors it is making.
Defines a connection to a data source.
A structure that is used to specify a connection to create or update.
The data structure used by the Data Catalog to encrypt the password as part of
CreateConnectionorUpdateConnectionand store it in theENCRYPTED_PASSWORDfield in the connection properties. You can enable catalog encryption or only password encryption.Specifies the connections used by a job.
The details of a crawl in the workflow.
Specifies a crawler program that examines a data source and uses classifiers to try to determine its schema. If successful, the crawler records metadata concerning the data source in the Glue Data Catalog.
Contains the information for a run of a crawler.
Metrics for a specified crawler.
The details of a Crawler node present in the workflow.
Specifies data stores to crawl.
A list of fields, comparators and value that you can use to filter the crawler runs for a specified crawler.
Specifies a custom CSV classifier for
CreateClassifierto create.Specifies a
grokclassifier forCreateClassifierto create.Specifies a JSON classifier for
CreateClassifierto create.Specifies an XML classifier for
CreateClassifierto create.A classifier for custom
CSVcontent.Specifies a transform that uses custom code you provide to perform the data transformation. The output is a collection of DynamicFrames.
An object representing a custom pattern for detecting sensitive data across the columns and rows of your structured data.
Contains configuration information for maintaining Data Catalog security.
The Lake Formation principal.
Additional run options you can specify for an evaluation run.
Describes a data quality result.
Describes a data quality result.
Criteria used to return data quality results.
Describes the result of a data quality rule recommendation run.
A filter for listing data quality recommendation runs.
Describes the result of the evaluation of a data quality rule.
Describes the result of a data quality ruleset evaluation run.
The filter criteria.
The criteria used to filter data quality rulesets.
Describes a data quality ruleset returned by
GetDataQualityRuleset.An object representing an Glue table.
A data source (an Glue table) for which you want data quality results.
The
Databaseobject represents a logical grouping of tables that might reside in a Hive metastore or an RDBMS.A structure that describes a target database for resource linking.
The structure used to create or update a database.
A structure representing the datatype of the value.
Defines column statistics supported for timestamp data columns.
Defines column statistics supported for fixed-point number data columns.
Contains a numeric value in decimal format.
Specifies a Delta data store to crawl one or more Delta tables.
A development endpoint where a developer can remotely debug extract, transform, and load (ETL) scripts.
Custom libraries to be loaded into a development endpoint.
Specifies the direct JDBC source connection.
Specifies an Apache Kafka data store.
Specifies a direct Amazon Kinesis data source.
A policy that specifies update behavior for the crawler.
Defines column statistics supported for floating-point number data columns.
Options to configure how your data quality evaluation results are published.
Options to configure how your job will stop if your data quality evaluation fails.
Specifies a transform that removes rows of repeating data from a data set.
Specifies a transform that chooses the data property keys that you want to drop.
Specifies a transform that removes columns from the dataset if all values in the column are 'null'. By default, Glue Studio will recognize null objects, but some values such as empty strings, strings that are "null", -1 integers or other placeholders such as zeros, are not automatically recognized as nulls.
Specifies the set of parameters needed to perform the dynamic transform.
Specifies a DynamoDB data source in the Glue Data Catalog.
Specifies an Amazon DynamoDB table to crawl.
An edge represents a directed connection between two Glue components that are part of the workflow the edge belongs to.
Specifies the encryption-at-rest configuration for the Data Catalog.
Specifies an encryption configuration.
Contains details about an error.
An object containing error details.
Specifies your data quality evaluation criteria.
Specifies your data quality evaluation criteria.
Evaluation metrics provide an estimate of the quality of your machine learning transform.
Batch condition that must be met (specified number of events received or batch time window expired) before EventBridge event trigger fires.
An execution property of a job.
Specifies configuration properties for an exporting labels task run.
A database that points to an entity outside the Glue Data Catalog.
A table that points to an entity outside the Glue Data Catalog.
Specifies a transform that locates records in the dataset that have missing values and adds a new field with a value determined by imputation. The input data set is used to train the machine learning model that determines what the missing value should be.
Specifies a transform that splits a dataset into two, based on a filter condition.
Specifies a filter expression.
Represents a single entry in the list of values for a
FilterExpression.The evaluation metrics for the find matches algorithm. The quality of your machine learning transform is measured by getting your transform to predict some matches and comparing the results to known matches from the same dataset. The quality metrics are based on a subset of your data, so they are not precise.
The parameters to configure the find matches transform.
Specifies configuration properties for a Find Matches task run.
Filters the connection definitions that are returned by the
GetConnectionsAPI operation.A structure for returning a resource policy.
Specifies a user-defined schema when a schema cannot be determined by Glue.
Specifies a single column in a Glue schema definition.
The database and table in the Glue Data Catalog that is used for input or output data.
Specifies the data store in the governed Glue Data Catalog.
Specifies a data target that writes to Amazon S3 using the Glue Data Catalog.
A classifier that uses
grokpatterns.Specifies an Apache Hudi data source.
A structure that defines an Apache Iceberg metadata table to create in the catalog.
Specifies an Apache Iceberg data source where Iceberg tables are stored in Amazon S3.
Specifies configuration properties for an importing labels task run.
Additional connection options for the connector.
Specifies a connector to a JDBC data source.
Specifies a data target that writes to Amazon S3 in Apache Parquet columnar storage.
Specifies a JDBC data store to crawl.
Specifies a job definition.
Defines a point that a job can resume processing.
Specifies how job bookmark data should be encrypted.
Specifies code that runs when a job is run.
The details of a Job node present in the workflow.
Contains information about a job run.
Specifies information used to update an existing job definition. The previous job definition is completely overwritten by this information.
Specifies a transform that joins two datasets into one dataset using a comparison phrase on the specified data property keys. You can use inner, outer, left, right, left semi, and left anti joins.
Specifies a column to be joined.
A classifier for
JSONcontent.Additional options for streaming.
A partition key pair consisting of a name and a type.
Additional options for the Amazon Kinesis streaming data source.
Specifies configuration properties for a labeling set generation task run.
Specifies Lake Formation configuration settings for the crawler.
When there are multiple versions of a blueprint and the latest version has some errors, this attribute indicates the last successful blueprint definition that is available with the service.
Status and error information about the most recent crawl.
Specifies data lineage configuration settings for the crawler.
The location of resources.
Defines column statistics supported for integer data columns.
Specifies the mapping of data property keys.
Defines a mapping.
Specifies a transform that merges a
DynamicFramewith a stagingDynamicFramebased on the specified primary keys to identify records. Duplicate records (records with the same primary keys) are not de-duplicated.A structure containing metadata information for a schema version.
A structure containing a key value pair for metadata.
Specifies a Microsoft SQL server data source in the Glue Data Catalog.
Specifies a target that uses Microsoft SQL.
A structure for a machine learning transform.
The encryption-at-rest settings of the transform that apply to accessing user data.
Specifies an Amazon DocumentDB or MongoDB data store to crawl.
Specifies a MySQL data source in the Glue Data Catalog.
Specifies a target that uses MySQL.
A node represents an Glue component (trigger, crawler, or job) on a workflow graph.
Specifies configuration properties of a notification.
Represents whether certain values are recognized as null values for removal.
Represents a custom null value such as a zeros or other value being used as a null placeholder unique to the dataset.
A structure representing an open format table.
Specifies an option value.
Specifies an Oracle data source in the Glue Data Catalog.
Specifies a target that uses Oracle SQL.
Specifies the sort order of a sorted column.
A structure containing other metadata for a schema version belonging to the same metadata key.
Represents a slice of table data.
Contains information about a partition error.
A structure for a partition index.
A descriptor for a partition index in a table.
The structure used to create and update a partition.
Contains a list of values defining partitions.
Specifies the physical requirements for a connection.
Specifies a transform that identifies, removes or masks PII data.
Specifies a PostgresSQL data source in the Glue Data Catalog.
Specifies a target that uses Postgres SQL.
A job run that was used in the predicate of a conditional trigger that triggered this job run.
Defines the predicate of the trigger, which determines when it fires.
Permissions granted to a principal.
Defines a property predicate.
A Glue Studio node that uses a Glue DataBrew recipe in Glue jobs.
A reference to a Glue DataBrew recipe.
When crawling an Amazon S3 data source after the first crawl is complete, specifies whether to crawl the entire dataset again or to crawl only folders that were added since the last crawler run. For more information, see Incremental Crawls in Glue in the developer guide.
Specifies an Amazon Redshift data store.
Specifies a target that uses Amazon Redshift.
A wrapper structure that may contain the registry name and Amazon Resource Name (ARN).
A structure containing the details for a registry.
Specifies a Relational database data source in the Glue Data Catalog.
Specifies a transform that renames a single data property key.
The URIs for function resources.
Specifies a Delta Lake data source that is registered in the Glue Data Catalog. The data source must be stored in Amazon S3.
Specifies a Hudi data source that is registered in the Glue Data Catalog. The Hudi data source must be stored in Amazon S3.
Specifies an Amazon S3 data store in the Glue Data Catalog.
Specifies a data target that writes to Amazon S3 using the Glue Data Catalog.
Specifies a command-separated value (CSV) data store stored in Amazon S3.
Specifies a target that writes to a Delta Lake data source in the Glue Data Catalog.
Specifies a target that writes to a Delta Lake data source in Amazon S3.
Specifies a Delta Lake data source stored in Amazon S3.
Specifies additional connection options for the Amazon S3 data store.
Specifies a data target that writes to Amazon S3.
Specifies how Amazon Simple Storage Service (Amazon S3) data should be encrypted.
Specifies a data target that writes to Amazon S3 in Apache Parquet columnar storage.
Specifies a target that writes to a Hudi data source in the Glue Data Catalog.
Specifies a target that writes to a Hudi data source in Amazon S3.
Specifies a Hudi data source stored in Amazon S3.
Specifies a JSON data store stored in Amazon S3.
Specifies an Apache Parquet data store stored in Amazon S3.
Specifies additional connection options for the Amazon S3 data store.
Specifies a data store in Amazon Simple Storage Service (Amazon S3).
A scheduling object using a
cronstatement to schedule an event.A policy that specifies update and deletion behaviors for the crawler.
A key-value pair representing a column and data type that this transform can run against. The
Schemaparameter of theMLTransformmay contain up to 100 of these structures.The unique ID of the schema in the Glue schema registry.
An object that contains minimal details for a schema.
An object that references a schema stored in the Glue Schema Registry.
An object that contains the error details for an operation on a schema version.
An object containing the details about a schema version.
A structure containing the schema version information.
Specifies a security configuration.
Defines a non-overlapping region of a table's partitions, allowing multiple requests to be run in parallel.
Specifies a transform that chooses the data property keys that you want to keep.
Specifies a transform that chooses one
DynamicFramefrom a collection ofDynamicFrames. The output is the selectedDynamicFrameInformation about a serialization/deserialization program (SerDe) that serves as an extractor and loader.
The period in which a remote Spark runtime environment is running.
The
SessionCommandthat runs the job.Specifies skewed values in a table. Skewed values are those that occur with very high frequency.
Specifies configuration for Snowflake nodes in Glue Studio.
Specifies a Snowflake data source.
Specifies a Snowflake target.
Specifies a field to sort by and a sort order.
The details for a source control configuration for a job, allowing synchronization of job artifacts to or from a remote repository.
Specifies a connector to an Apache Spark data source.
Specifies a target that uses an Apache Spark connector.
Specifies a transform where you enter a SQL query using Spark SQL syntax to transform the data. The output is a single
DynamicFrame.Specifies a transform that writes samples of the data to an Amazon S3 bucket.
Specifies a transform that splits data property keys into two
DynamicFrames. The output is a collection ofDynamicFrames: one with selected data property keys, and one with the remaining data property keys.Represents a single entry in the list of values for
SqlAliases.The batch condition that started the workflow run. Either the number of events in the batch size arrived, in which case the BatchSize member is non-zero, or the batch window expired, in which case the BatchWindow member is non-zero.
The statement or request for a particular action to occur in a session.
The code execution output in JSON format.
The code execution output in JSON format.
Describes the physical storage of table data.
Specifies options related to data preview for viewing a sample of your data.
Defines column statistics supported for character sequence data values.
Represents a collection of related data organized in columns and rows.
An error record for table operations.
A structure that describes a target table for resource linking.
A structure used to define a table.
Specifies a version of a table.
An error record for table-version operations.
The sampling parameters that are associated with the machine learning transform.
The criteria that are used to filter the task runs for the machine learning transform.
The configuration properties for the task run.
The sorting criteria that are used to sort the list of task runs for the machine learning transform.
Specifies the parameters in the config file of the dynamic transform.
The encryption-at-rest settings of the transform that apply to accessing user data. Machine learning transforms can access user data encrypted in Amazon S3 using KMS.
The criteria used to filter the machine learning transforms.
The algorithm-specific parameters that are associated with the machine learning transform.
The sorting criteria that are associated with the machine learning transform.
Information about a specific trigger.
The details of a Trigger node present in the workflow.
A structure used to provide information used to update a trigger. This object updates the previous trigger definition by overwriting it completely.
A partition that contains unfiltered metadata.
Specifies a transform that combines the rows from two or more datasets into a single result.
Specifies a custom CSV classifier to be updated.
Specifies a grok classifier to update when passed to
UpdateClassifier.Specifies a JSON classifier to be updated.
Specifies an XML classifier to be updated.
The options to configure an upsert operation when writing to a Redshift target .
Represents the equivalent of a Hive user-defined function (
UDF) definition.A structure used to create or update a user-defined function.
A workflow is a collection of multiple dependent Glue jobs and crawlers that are run to complete a complex ETL task. A workflow manages the execution and monitoring of all its jobs and crawlers.
A workflow graph represents the complete workflow containing all the Glue components present in the workflow and all the directed connections between them.
A workflow run is an execution of a workflow providing all the runtime information.
Workflow run statistics provides statistics about the workflow run.
A classifier for
XMLcontent.
Enums
- When writing a match expression against
AdditionalOptionKeys, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
AggFunction, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
BackfillErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
BlueprintRunState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
BlueprintStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CatalogEncryptionMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CloudWatchEncryptionMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ColumnStatisticsType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Comparator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Compatibility, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConnectionPropertyKey, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ConnectionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CrawlState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CrawlerHistoryState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CrawlerLineageSettings, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CrawlerState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
CsvHeaderOption, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DataFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DataQualityRuleResultStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DeleteBehavior, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DeltaTargetCompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DqStopJobOnFailureTiming, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
DqTransformOutput, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
EnableHybridValues, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ExecutionClass, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ExistCondition, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FederationSourceErrorCode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FieldName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterLogicalOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterOperation, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
FilterValueType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
GlueRecordType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
HudiTargetCompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JdbcConnectionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JdbcDataType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JdbcMetadataEntry, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JobBookmarksEncryptionMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JobRunState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
JoinType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Language, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
LastCrawlStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Logical, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
LogicalOperator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MetadataOperation, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
MlUserDataEncryptionModeString, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
NodeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ParamType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ParquetCompressionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PartitionIndexStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Permission, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PermissionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PiiType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
PrincipalType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
QuoteChar, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RecrawlBehavior, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
RegistryStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ResourceShareType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
S3EncryptionMode, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
ScheduleState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SchemaDiffType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SchemaStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SchemaVersionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Separator, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SessionStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
Sort, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SortDirectionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SourceControlAuthStrategy, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
SourceControlProvider, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
StartingPosition, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
StatementState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TargetFormat, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TaskRunSortColumnType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TaskStatusType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TaskType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TransformSortColumnType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TransformStatusType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TransformType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TriggerState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
TriggerType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UnionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UpdateBehavior, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
UpdateCatalogBehavior, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WorkerType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - When writing a match expression against
WorkflowRunStatus, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.