| |
<MatchRecordRule>
|
|
Refers to the first node of the MatchRecordRule file. It contains the SearchEntity node.
|
|
| |
SearchEntity
|
|
Includes the SearchMode, DataProvider, Repository details and their attributes that are considered in the duplicate detection process.
|
|
| |
|
Type
|
Specifies the search entity type. You can search records based on the search entity types based on the repository type.
|
The valid value is
table or
view. The default value is
table.
- Table: Used for a single repository duplicate detection
- View: Used for a cross-repository duplicate detection
|
| SearchMode
|
|
|
Specifies the search mode for scheduler duplicate detection. You can specify the following two modes:
- Complete: Specifies that for the first time search is performed on all data that exists in a repository. Next time onwards, the server verifies whether a scheduler duplicate detection (SDD) job was executed earlier, if yes, only new or changed records are searched. For example, the SDD job was executed on 12th April and the current SDD job execution date is 16th April. In this case, while detecting duplicate records, records are searched between 12th April and 16th April.
- Incremental: Specifies that only new or changed data is searched except in one case, that is, if an SDD job was not executed earlier, the server starts with the complete mode and the search is performed on the entire data.
|
The valid value is
Incremental or
Complete. The default value is Incremental.
|
| DataProvider
|
|
|
The class name of the data provider that returns a set of records in a batch.
Any custom data provider implementation must implement the IRecordExtractor interface and provide implementation of the following two methods:
-
public IBatchIterator getRecords(long catalogId,String searchMode,long eventId,String viewName) throws MqException;
public void closeIterator() throws MqException;
|
The valid value is any data provider class name. For example, com.tibco.dq.dao.DupDetectJobDataExtractor
|
| MatchAttributes
|
|
|
Name of the matching attributes and weightage. For example,
- Name: The name of the attribute. For example, BANKNAME
- Weight: Weight of the character that is specified in the Name attribute. For example, if the Weight value is
0.80.
|
The valid value for the
Name attribute is any valid string.
The valid value for the Weight attribute is a fraction between 0 and 1.
|
| DisplayAttributes
|
|
|
Name of the attributes that you want to display in the report.
|
The valid value is any valid attribute name.
|
| Relationship
|
|
|
Refers to the relationship name and related repository name.
|
The valid value is any valid string.
|
| MatchingThreshold
|
|
|
Refers to the matching score of the record.
The value indicates a minimum matching expectation. For example, if the MatchingThreshold value is set to
0.75, only records matching 75% or more are returned by the matching process.
|
The valid value is the minimum matching score value between 0 and 1.
|
| UseCustomQueryForNetrics
(Optional)
|
<UseCustomQueryForNetrics>
|
|
If specified as
True, the custom Netrics query specified in the CustomNetricsQueryBuilderImpl parameter is used to get results from the Netrics indexes.
|
True
False (Default)
|
| CustomNetricsQueryBuilderImpl
(Optional)
|
<CustomNetricsQueryBuilderImpl>
|
|
Use the custom implementation class to query the Netrics table. It should implement com.tibco.mdm.repository.
search.INetricsQueryBuilder interface.
|
The Java class name that you want to load.
|
| IndexEntityNameTo
Search
(Optional) - Do not work with View Type.
|
<IndexEntityNameToSearch>
|
|
Allows to search the custom index entity. While searching the index entities, the specified index entity name is used for searching records instead of an auto detection.
|
Index entity name that is specified in the
IndexerConfig.xml file. For example, Customer_IndexEntity.
|
