@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 in a matching workflow. RuleBasedProperties contain a
Rules
field, 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()
The comparison type.
|
String |
getMatchPurpose()
An indicator of whether to generate IDs and index the data or not.
|
List<Rule> |
getRules()
A list of
Rule objects, each of which have fields RuleName and
MatchingKeys . |
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller . |
void |
setAttributeMatchingModel(String attributeMatchingModel)
The comparison type.
|
void |
setMatchPurpose(String matchPurpose)
An indicator of whether to generate IDs and index the data or not.
|
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 |
withMatchPurpose(MatchPurpose matchPurpose)
An indicator of whether to generate IDs and index the data or not.
|
RuleBasedProperties |
withMatchPurpose(String matchPurpose)
An indicator of whether to generate IDs and index the data or not.
|
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)
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 and the value of
BusinessEmail
field of Profile B matches, 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.
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 and the value of
BusinessEmail
field of Profile B matches, 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.
AttributeMatchingModel
public String getAttributeMatchingModel()
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 and the value of
BusinessEmail
field of Profile B matches, 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.
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 and the value of
BusinessEmail
field of Profile B matches, 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.
AttributeMatchingModel
public RuleBasedProperties withAttributeMatchingModel(String 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 and the value of
BusinessEmail
field of Profile B matches, 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.
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 and the value of
BusinessEmail
field of Profile B matches, 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.
AttributeMatchingModel
public RuleBasedProperties withAttributeMatchingModel(AttributeMatchingModel 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 and the value of
BusinessEmail
field of Profile B matches, 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.
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 and the value of
BusinessEmail
field of Profile B matches, 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.
AttributeMatchingModel
public void setMatchPurpose(String matchPurpose)
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
matchPurpose
- An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
MatchPurpose
public String getMatchPurpose()
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
MatchPurpose
public RuleBasedProperties withMatchPurpose(String matchPurpose)
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
matchPurpose
- An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
MatchPurpose
public RuleBasedProperties withMatchPurpose(MatchPurpose matchPurpose)
An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
matchPurpose
- An indicator of whether to generate IDs and index the data or not.
If you choose IDENTIFIER_GENERATION
, the process generates IDs and indexes the data.
If you choose INDEXING
, the process indexes the data without generating IDs.
MatchPurpose
public List<Rule> getRules()
A list of Rule
objects, each of which have fields RuleName
and
MatchingKeys
.
Rule
objects, each of which have fields 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 Object
Object.toString()
public RuleBasedProperties clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojo
ProtocolMarshaller
.marshall
in interface StructuredPojo
protocolMarshaller
- Implementation of ProtocolMarshaller
used to marshall this object's data.