Struct aws_sdk_entityresolution::types::builders::RuleBasedPropertiesBuilder

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

A builder for RuleBasedProperties.

Implementations

impl RuleBasedPropertiesBuilder

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

Appends an item to rules.

To override the contents of this collection use set_rules.

A list of Rule objects, each of which have fields RuleName and MatchingKeys.

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

A list of Rule objects, each of which have fields RuleName and MatchingKeys.

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

A list of Rule objects, each of which have fields RuleName and MatchingKeys.

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. When choosing 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 and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email type. When choosing ONE_TO_ONE ,the system can only match if the sub-types are exact matches. For example, only when the value of the Email field of Profile A and the value of the Email field of Profile B matches, the two profiles are matched on the Email type.

This field is required.

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. When choosing 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 and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email type. When choosing ONE_TO_ONE ,the system can only match if the sub-types are exact matches. For example, only when the value of the Email field of Profile A and the value of the Email field of Profile B matches, the two profiles are matched on the Email type.

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. When choosing 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 and the value of BusinessEmail field of Profile B matches, the two profiles are matched on the Email type. When choosing ONE_TO_ONE ,the system can only match if the sub-types are exact matches. For example, only when the value of the Email field of Profile A and the value of the Email field of Profile B matches, the two profiles are matched on the Email type.

pub fn build(self) -> Result<RuleBasedProperties, BuildError>

Consumes the builder and constructs a RuleBasedProperties. This method will fail if any of the following fields are not set:

• rules
• attribute_matching_model

Trait Implementations

impl Clone for RuleBasedPropertiesBuilder

fn clone(&self) -> RuleBasedPropertiesBuilder

Returns a copy of the value.

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

Performs copy-assignment from source.

impl Debug for RuleBasedPropertiesBuilder

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

Formats the value using the given formatter.

impl Default for RuleBasedPropertiesBuilder

fn default() -> RuleBasedPropertiesBuilder

Returns the “default value” for a type.

impl PartialEq for RuleBasedPropertiesBuilder

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

This method tests for self and other values to be equal, and is used by ==.

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

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

impl StructuralPartialEq for RuleBasedPropertiesBuilder