@Generated(value="com.amazonaws:aws-java-sdk-code-generator") public class NamespaceRuleBasedProperties extends Object implements Serializable, Cloneable, StructuredPojo
The rule-based properties of an ID namespace. These properties define how the ID namespace can be used in an ID mapping workflow.
| Constructor and Description |
|---|
NamespaceRuleBasedProperties() |
| Modifier and Type | Method and Description |
|---|---|
NamespaceRuleBasedProperties |
clone() |
boolean |
equals(Object obj) |
String |
getAttributeMatchingModel()
The comparison type.
|
List<String> |
getRecordMatchingModels()
The type of matching record that is allowed to be used in an ID mapping workflow.
|
List<String> |
getRuleDefinitionTypes()
The sets of rules you can use in an ID mapping workflow.
|
List<Rule> |
getRules()
The rules for the ID namespace.
|
int |
hashCode() |
void |
marshall(ProtocolMarshaller protocolMarshaller)
Marshalls this structured data using the given
ProtocolMarshaller. |
void |
setAttributeMatchingModel(String attributeMatchingModel)
The comparison type.
|
void |
setRecordMatchingModels(Collection<String> recordMatchingModels)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
void |
setRuleDefinitionTypes(Collection<String> ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow.
|
void |
setRules(Collection<Rule> rules)
The rules for the ID namespace.
|
String |
toString()
Returns a string representation of this object.
|
NamespaceRuleBasedProperties |
withAttributeMatchingModel(AttributeMatchingModel attributeMatchingModel)
The comparison type.
|
NamespaceRuleBasedProperties |
withAttributeMatchingModel(String attributeMatchingModel)
The comparison type.
|
NamespaceRuleBasedProperties |
withRecordMatchingModels(Collection<String> recordMatchingModels)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRecordMatchingModels(RecordMatchingModel... recordMatchingModels)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRecordMatchingModels(String... recordMatchingModels)
The type of matching record that is allowed to be used in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRuleDefinitionTypes(Collection<String> ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRuleDefinitionTypes(IdMappingWorkflowRuleDefinitionType... ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRuleDefinitionTypes(String... ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow.
|
NamespaceRuleBasedProperties |
withRules(Collection<Rule> rules)
The rules for the ID namespace.
|
NamespaceRuleBasedProperties |
withRules(Rule... rules)
The rules for the ID namespace.
|
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 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.
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.
AttributeMatchingModelpublic 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 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.
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.
AttributeMatchingModelpublic NamespaceRuleBasedProperties 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 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.
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.
AttributeMatchingModelpublic NamespaceRuleBasedProperties 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 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.
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.
AttributeMatchingModelpublic List<String> getRecordMatchingModels()
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.
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.
RecordMatchingModelpublic void setRecordMatchingModels(Collection<String> recordMatchingModels)
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.
recordMatchingModels - 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.
RecordMatchingModelpublic NamespaceRuleBasedProperties withRecordMatchingModels(String... recordMatchingModels)
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.
NOTE: This method appends the values to the existing list (if any). Use
setRecordMatchingModels(java.util.Collection) or withRecordMatchingModels(java.util.Collection)
if you want to override the existing values.
recordMatchingModels - 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.
RecordMatchingModelpublic NamespaceRuleBasedProperties withRecordMatchingModels(Collection<String> recordMatchingModels)
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.
recordMatchingModels - 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.
RecordMatchingModelpublic NamespaceRuleBasedProperties withRecordMatchingModels(RecordMatchingModel... recordMatchingModels)
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.
recordMatchingModels - 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.
RecordMatchingModelpublic List<String> getRuleDefinitionTypes()
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
IdMappingWorkflowRuleDefinitionTypepublic void setRuleDefinitionTypes(Collection<String> ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
ruleDefinitionTypes - The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and
target must be compatible.IdMappingWorkflowRuleDefinitionTypepublic NamespaceRuleBasedProperties withRuleDefinitionTypes(String... ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
NOTE: This method appends the values to the existing list (if any). Use
setRuleDefinitionTypes(java.util.Collection) or withRuleDefinitionTypes(java.util.Collection)
if you want to override the existing values.
ruleDefinitionTypes - The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and
target must be compatible.IdMappingWorkflowRuleDefinitionTypepublic NamespaceRuleBasedProperties withRuleDefinitionTypes(Collection<String> ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
ruleDefinitionTypes - The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and
target must be compatible.IdMappingWorkflowRuleDefinitionTypepublic NamespaceRuleBasedProperties withRuleDefinitionTypes(IdMappingWorkflowRuleDefinitionType... ruleDefinitionTypes)
The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and target must be compatible.
ruleDefinitionTypes - The sets of rules you can use in an ID mapping workflow. The limitations specified for the source and
target must be compatible.IdMappingWorkflowRuleDefinitionTypepublic List<Rule> getRules()
The rules for the ID namespace.
public void setRules(Collection<Rule> rules)
The rules for the ID namespace.
rules - The rules for the ID namespace.public NamespaceRuleBasedProperties withRules(Rule... rules)
The rules for the ID namespace.
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 - The rules for the ID namespace.public NamespaceRuleBasedProperties withRules(Collection<Rule> rules)
The rules for the ID namespace.
rules - The rules for the ID namespace.public String toString()
toString in class ObjectObject.toString()public NamespaceRuleBasedProperties clone()
public void marshall(ProtocolMarshaller protocolMarshaller)
StructuredPojoProtocolMarshaller.marshall in interface StructuredPojoprotocolMarshaller - Implementation of ProtocolMarshaller used to marshall this object's data.