Module aws_sdk_entityresolution::types

Data structures used by operation inputs/outputs.

Modules

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

Structs

• ErrorDetails

  An object containing an error message, if there was an error.

• IncrementalRunConfig

  An object which defines an incremental run type and has only incrementalRunType as a field.

• InputSource

  An object containing InputSourceARN, SchemaName, and ApplyNormalization.

• JobMetrics

  An object containing InputRecords, TotalRecordsProcessed, MatchIDs, and RecordsNotProcessed.

• JobSummary

  An object containing the JobId, Status, StartTime, and EndTime of a job.

• MatchingWorkflowSummary

  A list of MatchingWorkflowSummary objects, each of which contain the fields WorkflowName, WorkflowArn, CreatedAt, UpdatedAt.

• OutputAttribute

  A list of OutputAttribute objects, each of which have the fields Name and Hashed. Each of these objects selects a column to be included in the output table, and whether the values of the column should be hashed.

• OutputSource

  A list of OutputAttribute objects, each of which have the fields Name and Hashed. Each of these objects selects a column to be included in the output table, and whether the values of the column should be hashed.

• ResolutionTechniques

  An object which defines the resolutionType and the ruleBasedProperties.

• Rule

  An object containing RuleName, and MatchingKeys.

• RuleBasedProperties

  An object which defines the list of matching rules to run and has a field Rules, which is a list of rule objects.

• SchemaInputAttribute

  An object containing FieldField, Type, GroupName, and MatchKey.

• SchemaMappingSummary

  An object containing SchemaName, SchemaArn, CreatedAt, andUpdatedAt.

Enums

• AttributeMatchingModel
  When writing a match expression against AttributeMatchingModel, 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.
• IncrementalRunType
  When writing a match expression against IncrementalRunType, 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.
• JobStatus
  When writing a match expression against JobStatus, 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.
• ResolutionType
  When writing a match expression against ResolutionType, 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.
• SchemaAttributeType
  When writing a match expression against SchemaAttributeType, 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.