com.amazonaws.services.entityresolution.model

Class RuleBasedProperties

java.lang.Object

com.amazonaws.services.entityresolution.model.RuleBasedProperties

All Implemented Interfaces:

StructuredPojo, Serializable, Cloneable

@Generated(value="com.amazonaws:aws-java-sdk-code-generator")
public class RuleBasedProperties
extends Object
implements Serializable, Cloneable, StructuredPojo

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

See Also:

AWS API Documentation, Serialized Form

Constructor Summary

Constructors

Constructor and Description
RuleBasedProperties()

Method Summary

Modifier and Type	Method and Description
RuleBasedProperties	clone()
boolean	equals(Object obj)
String	getAttributeMatchingModel() The comparison type.
List<Rule>	getRules() A list of Rule objects, each of which have fields RuleName and MatchingKeys.
int	hashCode()
void	marshall(ProtocolMarshaller protocolMarshaller)
void	setAttributeMatchingModel(String attributeMatchingModel) The comparison type.
void	setRules(Collection<Rule> rules) A list of Rule objects, each of which have fields RuleName and MatchingKeys.
String	toString() Returns a string representation of this object.
RuleBasedProperties	withAttributeMatchingModel(AttributeMatchingModel attributeMatchingModel) The comparison type.
RuleBasedProperties	withAttributeMatchingModel(String attributeMatchingModel) The comparison type.
RuleBasedProperties	withRules(Collection<Rule> rules) A list of Rule objects, each of which have fields RuleName and MatchingKeys.
RuleBasedProperties	withRules(Rule... rules) A list of Rule objects, each of which have fields RuleName and MatchingKeys.

Methods inherited from class java.lang.Object

finalize, getClass, notify, notifyAll, wait, wait, wait

Constructor Detail

RuleBasedProperties

public RuleBasedProperties()

Method Detail

setAttributeMatchingModel

public void setAttributeMatchingModel(String 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.

Parameters:

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.

See Also:

AttributeMatchingModel

getAttributeMatchingModel

public String getAttributeMatchingModel()

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.

Returns:

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.

See Also:

AttributeMatchingModel

withAttributeMatchingModel

public RuleBasedProperties withAttributeMatchingModel(String 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.

Parameters:

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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

AttributeMatchingModel

withAttributeMatchingModel

public RuleBasedProperties withAttributeMatchingModel(AttributeMatchingModel 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.

Parameters:

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.

Returns:

Returns a reference to this object so that method calls can be chained together.

See Also:

AttributeMatchingModel

getRules

public List<Rule> getRules()

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

Returns:

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

setRules

public void setRules(Collection<Rule> rules)

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

Parameters:

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

withRules

public RuleBasedProperties withRules(Rule... rules)

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

NOTE: This method appends the values to the existing list (if any). Use setRules(java.util.Collection) or withRules(java.util.Collection) if you want to override the existing values.

Parameters:

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

Returns:

Returns a reference to this object so that method calls can be chained together.

withRules

public RuleBasedProperties withRules(Collection<Rule> rules)

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

Parameters:

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

Returns:

Returns a reference to this object so that method calls can be chained together.

toString

public String toString()

Returns a string representation of this object. This is useful for testing and debugging. Sensitive data will be redacted from this string using a placeholder value.

Overrides:

toString in class Object

Returns:

A string representation of this object.

See Also:

Object.toString()

equals

public boolean equals(Object obj)

Overrides:

equals in class Object

hashCode

public int hashCode()

Overrides:

hashCode in class Object

clone

public RuleBasedProperties clone()

Overrides:

clone in class Object

marshall

public void marshall(ProtocolMarshaller protocolMarshaller)

Specified by:

marshall in interface StructuredPojo