interface NamespaceRuleBasedPropertiesProperty
| Language | Type name | 
|---|---|
|  .NET | Amazon.CDK.aws_entityresolution.CfnIdNamespace.NamespaceRuleBasedPropertiesProperty | 
|  Go | github.com/aws/aws-cdk-go/awscdk/v2/awsentityresolution#CfnIdNamespace_NamespaceRuleBasedPropertiesProperty | 
|  Java | software.amazon.awscdk.services.entityresolution.CfnIdNamespace.NamespaceRuleBasedPropertiesProperty | 
|  Python | aws_cdk.aws_entityresolution.CfnIdNamespace.NamespaceRuleBasedPropertiesProperty | 
|  TypeScript | aws-cdk-lib»aws_entityresolution»CfnIdNamespace»NamespaceRuleBasedPropertiesProperty | 
The rule-based properties of an ID namespace.
These properties define how the ID namespace can be used in an ID mapping workflow.
Example
// The code below shows an example of how to instantiate this type.
// The values are placeholders you should change.
import { aws_entityresolution as entityresolution } from 'aws-cdk-lib';
const namespaceRuleBasedPropertiesProperty: entityresolution.CfnIdNamespace.NamespaceRuleBasedPropertiesProperty = {
  attributeMatchingModel: 'attributeMatchingModel',
  recordMatchingModels: ['recordMatchingModels'],
  ruleDefinitionTypes: ['ruleDefinitionTypes'],
  rules: [{
    matchingKeys: ['matchingKeys'],
    ruleName: 'ruleName',
  }],
};
Properties
| Name | Type | Description | 
|---|---|---|
| attribute | string | The comparison type. You can either choose ONE_TO_ONEorMANY_TO_MANYas theattributeMatchingModel. | 
| record | string[] | The type of matching record that is allowed to be used in an ID mapping workflow. | 
| rule | string[] | The sets of rules you can use in an ID mapping workflow. | 
| rules? | IResolvable | (IResolvable | Rule)[] | The rules for the ID namespace. | 
attributeMatchingModel?
Type:
string
(optional)
The comparison type. You can either choose ONE_TO_ONE or MANY_TO_MANY as the attributeMatchingModel .
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.
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.
recordMatchingModels?
Type:
string[]
(optional)
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.
ruleDefinitionTypes?
Type:
string[]
(optional)
The sets of rules you can use in an ID mapping workflow.
The limitations specified for the source and target must be compatible.
rules?
Type:
IResolvable | (IResolvable | Rule)[]
(optional)
The rules for the ID namespace.
