@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.
| Constructor and Description |
|---|
RuleBasedProperties() |
| Modifier and Type | Method and Description |
|---|---|
RuleBasedProperties |
clone() |
boolean |
equals(Object obj) |
String |
getAttributeMatchingModel()
You can either choose
ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. |
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)
You can either choose
ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. |
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)
You can either choose
ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. |
RuleBasedProperties |
withAttributeMatchingModel(String attributeMatchingModel)
You can either choose
ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. |
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. |
public void setAttributeMatchingModel(String attributeMatchingModel)
You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When
choosing MANY_TO_MANY, the system can match attribute 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.
attributeMatchingModel - You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel.
When choosing MANY_TO_MANY, the system can match attribute 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.AttributeMatchingModelpublic String getAttributeMatchingModel()
You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When
choosing MANY_TO_MANY, the system can match attribute 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.
ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel.
When choosing MANY_TO_MANY, the system can match attribute 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.AttributeMatchingModelpublic RuleBasedProperties withAttributeMatchingModel(String attributeMatchingModel)
You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When
choosing MANY_TO_MANY, the system can match attribute 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.
attributeMatchingModel - You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel.
When choosing MANY_TO_MANY, the system can match attribute 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.AttributeMatchingModelpublic RuleBasedProperties withAttributeMatchingModel(AttributeMatchingModel attributeMatchingModel)
You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel. When
choosing MANY_TO_MANY, the system can match attribute 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.
attributeMatchingModel - You can either choose ONE_TO_ONE or MANY_TO_MANY as the AttributeMatchingModel.
When choosing MANY_TO_MANY, the system can match attribute 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.AttributeMatchingModelpublic List<Rule> getRules()
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
RuleName and MatchingKeys.public void setRules(Collection<Rule> rules)
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
rules - A list of Rule objects, each of which have fields RuleName and MatchingKeys.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.
rules - A list of Rule objects, each of which have fields RuleName and MatchingKeys.public RuleBasedProperties withRules(Collection<Rule> rules)
A list of Rule objects, each of which have fields RuleName and MatchingKeys.
rules - A list of Rule objects, each of which have fields RuleName and MatchingKeys.public String toString()
toString in class ObjectObject.toString()public RuleBasedProperties clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
marshall in interface StructuredPojoCopyright © 2023. All rights reserved.