Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Glue DataBrew can respond with.

Structs

• AllowedStatistics

  Configuration of statistics that are allowed to be run on columns that contain detected entities. When undefined, no statistics will be computed on columns that contain detected entities.

• ColumnSelector

  Selector of a column from a dataset for profile job configuration. One selector includes either a column name or a regular expression.

• ColumnStatisticsConfiguration

  Configuration for column evaluations for a profile job. ColumnStatisticsConfiguration can be used to select evaluations and override parameters of evaluations for particular columns.

• ConditionExpression

  Represents an individual condition that evaluates to true or false.

  Conditions are used with recipe actions. The action is only performed for column values where the condition evaluates to true.

  If a recipe requires more than one condition, then the recipe must specify multiple ConditionExpression elements. Each condition is applied to the rows in a dataset first, before the recipe action is performed.

• CsvOptions

  Represents a set of options that define how DataBrew will read a comma-separated value (CSV) file when creating a dataset from that file.

• CsvOutputOptions

  Represents a set of options that define how DataBrew will write a comma-separated value (CSV) file.

• DataCatalogInputDefinition

  Represents how metadata stored in the Glue Data Catalog is defined in a DataBrew dataset.

• DataCatalogOutput

  Represents options that specify how and where in the Glue Data Catalog DataBrew writes the output generated by recipe jobs.

• DatabaseInputDefinition

  Connection information for dataset input files stored in a database.

• DatabaseOutput

  Represents a JDBC database output object which defines the output destination for a DataBrew recipe job to write into.

• DatabaseTableOutputOptions

  Represents options that specify how and where DataBrew writes the database output generated by recipe jobs.

• Dataset

  Represents a dataset that can be processed by DataBrew.

• DatasetParameter

  Represents a dataset parameter that defines type and conditions for a parameter in the Amazon S3 path of the dataset.

• DatetimeOptions

  Represents additional options for correct interpretation of datetime parameters used in the Amazon S3 path of a dataset.

• EntityDetectorConfiguration

  Configuration of entity detection for a profile job. When undefined, entity detection is disabled.

• ExcelOptions

  Represents a set of options that define how DataBrew will interpret a Microsoft Excel file when creating a dataset from that file.

• FilesLimit

  Represents a limit imposed on number of Amazon S3 files that should be selected for a dataset from a connected Amazon S3 path.

• FilterExpression

  Represents a structure for defining parameter conditions. Supported conditions are described here: Supported conditions for dynamic datasets in the Glue DataBrew Developer Guide.

• FormatOptions

  Represents a set of options that define the structure of either comma-separated value (CSV), Excel, or JSON input.

• Input

  Represents information on how DataBrew can find data, in either the Glue Data Catalog or Amazon S3.

• Job

  Represents all of the attributes of a DataBrew job.

• JobRun

  Represents one run of a DataBrew job.

• JobSample

  A sample configuration for profile jobs only, which determines the number of rows on which the profile job is run. If a JobSample value isn't provided, the default is used. The default value is CUSTOM_ROWS for the mode parameter and 20,000 for the size parameter.

• JsonOptions

  Represents the JSON-specific options that define how input is to be interpreted by Glue DataBrew.

• Metadata

  Contains additional resource information needed for specific datasets.

• Output

  Represents options that specify how and where in Amazon S3 DataBrew writes the output generated by recipe jobs or profile jobs.

• OutputFormatOptions

  Represents a set of options that define the structure of comma-separated (CSV) job output.

• PathOptions

  Represents a set of options that define how DataBrew selects files for a given Amazon S3 path in a dataset.

• ProfileConfiguration

  Configuration for profile jobs. Configuration can be used to select columns, do evaluations, and override default parameters of evaluations. When configuration is undefined, the profile job will apply default settings to all supported columns.

• Project

  Represents all of the attributes of a DataBrew project.

• Recipe

  Represents one or more actions to be performed on a DataBrew dataset.

• RecipeAction

  Represents a transformation and associated parameters that are used to apply a change to a DataBrew dataset. For more information, see Recipe actions reference.

• RecipeReference

  Represents the name and version of a DataBrew recipe.

• RecipeStep

  Represents a single step from a DataBrew recipe to be performed.

• RecipeVersionErrorDetail

  Represents any errors encountered when attempting to delete multiple recipe versions.

• Rule

  Represents a single data quality requirement that should be validated in the scope of this dataset.

• RulesetItem

  Contains metadata about the ruleset.

• S3Location

  Represents an Amazon S3 location (bucket name, bucket owner, and object key) where DataBrew can read input data, or write output from a job.

• S3TableOutputOptions

  Represents options that specify how and where DataBrew writes the Amazon S3 output generated by recipe jobs.

• Sample

  Represents the sample size and sampling type for DataBrew to use for interactive data analysis.

• Schedule

  Represents one or more dates and times when a job is to run.

• StatisticOverride

  Override of a particular evaluation for a profile job.

• StatisticsConfiguration

  Configuration of evaluations for a profile job. This configuration can be used to select evaluations and override the parameters of selected evaluations.

• Threshold

  The threshold used with a non-aggregate check expression. The non-aggregate check expression will be applied to each row in a specific column. Then the threshold will be used to determine whether the validation succeeds.

• ValidationConfiguration

  Configuration for data quality validation. Used to select the Rulesets and Validation Mode to be used in the profile job. When ValidationConfiguration is null, the profile job will run without data quality validation.

• ViewFrame

  Represents the data being transformed during an action.

Enums

• AnalyticsMode
  When writing a match expression against AnalyticsMode, 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.
• CompressionFormat
  When writing a match expression against CompressionFormat, 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.
• DatabaseOutputMode
  When writing a match expression against DatabaseOutputMode, 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.
• EncryptionMode
  When writing a match expression against EncryptionMode, 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.
• InputFormat
  When writing a match expression against InputFormat, 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.
• JobRunState
  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.
• JobType
  When writing a match expression against JobType, 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.
• LogSubscription
  When writing a match expression against LogSubscription, 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.
• Order
  When writing a match expression against Order, 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.
• OrderedBy
  When writing a match expression against OrderedBy, 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.
• OutputFormat
  When writing a match expression against OutputFormat, 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.
• ParameterType
  When writing a match expression against ParameterType, 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.
• SampleMode
  When writing a match expression against SampleMode, 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.
• SampleType
  When writing a match expression against SampleType, 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.
• SessionStatus
  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.
• Source
  When writing a match expression against Source, 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.
• ThresholdType
  When writing a match expression against ThresholdType, 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.
• ThresholdUnit
  When writing a match expression against ThresholdUnit, 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.
• ValidationMode
  When writing a match expression against ValidationMode, 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.