Expand description

Data structures used by operation inputs/outputs.

Modules§

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

Structs§

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

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

  • An object which defines the ID mapping techniques and provider configurations.

  • An object containing InputSourceARN and SchemaName.

  • The output source for the ID mapping workflow.

  • A list of IdMappingWorkflowSummary objects, each of which contain the fields WorkflowName, WorkflowArn, CreatedAt, and UpdatedAt.

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

  • An object containing InputSourceARN, SchemaName, and ApplyNormalization.

  • The Amazon S3 location that temporarily stores your data while it processes. Your information won't be saved permanently.

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

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

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

  • 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.

  • 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.

  • The required configuration fields to give intermediate access to a provider service.

  • The identifiers of the provider service, from Data Exchange.

  • An object containing the providerServiceARN, intermediateSourceConfiguration, and providerConfiguration.

  • A list of ProviderService objects, each of which contain the fields providerName, providerServiceArn, providerServiceName, and providerServiceType.

  • An object which defines the resolutionType and the ruleBasedProperties.

  • An object containing RuleName, and MatchingKeys.

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

  • An object containing FieldName, Type, GroupName, and MatchKey.

  • An object containing SchemaName, SchemaArn, CreatedAt, andUpdatedAt.

Enums§

  • 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.
  • When writing a match expression against IdMappingType, 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 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.
  • 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.
  • The required configuration fields to use with the provider service.

  • 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.
  • 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.
  • When writing a match expression against ServiceType, 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.