Struct aws_sdk_entityresolution::types::NamespaceRuleBasedProperties

#[non_exhaustive]
pub struct NamespaceRuleBasedProperties {
    pub rules: Option<Vec<Rule>>,
    pub rule_definition_types: Option<Vec<IdMappingWorkflowRuleDefinitionType>>,
    pub attribute_matching_model: Option<AttributeMatchingModel>,
    pub record_matching_models: Option<Vec<RecordMatchingModel>>,
}

The rule-based properties of an ID namespace. These properties define how the ID namespace can be used in an ID mapping workflow.

Fields (Non-exhaustive)

Non-exhaustive structs could have additional fields added in future. Therefore, non-exhaustive structs cannot be constructed in external crates using the traditional Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.

rules: Option<Vec<Rule>>

The rules for the ID namespace.

rule_definition_types: Option<Vec<IdMappingWorkflowRuleDefinitionType>>

The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.

attribute_matching_model: Option<AttributeMatchingModel>

The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A matches the value of BusinessEmail field of Profile B, the two profiles are matched on the Email attribute type.

If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

record_matching_models: Option<Vec<RecordMatchingModel>>

The type of matching record that is allowed to be used in an ID mapping workflow.

If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source is matched to one record in the target.

If the value is set to MANY_SOURCE_TO_ONE_TARGET, all matching records in the source are matched to one record in the target.

Implementations

impl NamespaceRuleBasedProperties

pub fn rules(&self) -> &[Rule]

The rules for the ID namespace.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .rules.is_none().

pub fn rule_definition_types(&self) -> &[IdMappingWorkflowRuleDefinitionType]

The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .rule_definition_types.is_none().

pub fn attribute_matching_model(&self) -> Option<&AttributeMatchingModel>

The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel.

If you choose MANY_TO_MANY, the system can match attributes across the sub-types of an attribute type. For example, if the value of the Email field of Profile A matches the value of BusinessEmail field of Profile B, the two profiles are matched on the Email attribute type.

If you choose ONE_TO_ONE, the system can only match attributes if the sub-types are an exact match. For example, for the Email attribute type, the system will only consider it a match if the value of the Email field of Profile A matches the value of the Email field of Profile B.

pub fn record_matching_models(&self) -> &[RecordMatchingModel]

The type of matching record that is allowed to be used in an ID mapping workflow.

If the value is set to ONE_SOURCE_TO_ONE_TARGET, only one record in the source is matched to one record in the target.

If the value is set to MANY_SOURCE_TO_ONE_TARGET, all matching records in the source are matched to one record in the target.

If no value was sent for this field, a default will be set. If you want to determine if no value was sent, use .record_matching_models.is_none().

impl NamespaceRuleBasedProperties

pub fn builder() -> NamespaceRuleBasedPropertiesBuilder

Creates a new builder-style object to manufacture NamespaceRuleBasedProperties.

Trait Implementations

impl Clone for NamespaceRuleBasedProperties

fn clone(&self) -> NamespaceRuleBasedProperties

Returns a copy of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for NamespaceRuleBasedProperties

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl PartialEq for NamespaceRuleBasedProperties

fn eq(&self, other: &NamespaceRuleBasedProperties) -> bool

Tests for self and other values to be equal, and is used by ==.

fn ne(&self, other: &Rhs) -> bool

Tests for !=. The default implementation is almost always sufficient, and should not be overridden without very good reason.

impl StructuralPartialEq for NamespaceRuleBasedProperties