Struct aws_sdk_entityresolution::types::builders::NamespaceRuleBasedPropertiesBuilder

#[non_exhaustive]
pub struct NamespaceRuleBasedPropertiesBuilder { /* private fields */ }

A builder for NamespaceRuleBasedProperties.

Implementations

impl NamespaceRuleBasedPropertiesBuilder

pub fn rules(self, input: Rule) -> Self

Appends an item to rules.

To override the contents of this collection use set_rules.

The rules for the ID namespace.

pub fn set_rules(self, input: Option<Vec<Rule>>) -> Self

The rules for the ID namespace.

pub fn get_rules(&self) -> &Option<Vec<Rule>>

The rules for the ID namespace.

pub fn rule_definition_types( self, input: IdMappingWorkflowRuleDefinitionType, ) -> Self

Appends an item to rule_definition_types.

To override the contents of this collection use set_rule_definition_types.

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

pub fn set_rule_definition_types( self, input: Option<Vec<IdMappingWorkflowRuleDefinitionType>>, ) -> Self

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

pub fn get_rule_definition_types( &self, ) -> &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.

pub fn attribute_matching_model(self, input: AttributeMatchingModel) -> Self

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 set_attribute_matching_model( self, input: Option<AttributeMatchingModel>, ) -> Self

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 get_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, input: RecordMatchingModel) -> Self

Appends an item to record_matching_models.

To override the contents of this collection use set_record_matching_models.

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.

pub fn set_record_matching_models( self, input: Option<Vec<RecordMatchingModel>>, ) -> Self

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.

pub fn get_record_matching_models(&self) -> &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.

pub fn build(self) -> NamespaceRuleBasedProperties

Consumes the builder and constructs a NamespaceRuleBasedProperties.

Trait Implementations

impl Clone for NamespaceRuleBasedPropertiesBuilder

fn clone(&self) -> NamespaceRuleBasedPropertiesBuilder

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for NamespaceRuleBasedPropertiesBuilder

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

Formats the value using the given formatter.

impl Default for NamespaceRuleBasedPropertiesBuilder

fn default() -> NamespaceRuleBasedPropertiesBuilder

Returns the “default value” for a type.

impl PartialEq for NamespaceRuleBasedPropertiesBuilder

fn eq(&self, other: &NamespaceRuleBasedPropertiesBuilder) -> 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 NamespaceRuleBasedPropertiesBuilder