Resolving Potential Match Inconsistencies with the Potential Matches Reindex Task

Problem

Inconsistencies in potential match counters can arise due to various factors, leading to inaccurate match evaluations.

Solution

To address these inconsistencies, Reltio provides the Potential Matches Reindex Task, which reindexes potential match information from scratch using match tables. This task cleans the potential match data in Elasticsearch and rebuilds it to ensure accuracy.

Usage:

1. Triggering the Task:
   • Admin Role: POST {ApplicationURL}/rebuildpmcounters
   • Tenant Admin Role: POST {ApplicationURL}/api/{tenantId}/rebuildpmcounters
2. Parameters:
   • tenantId (Required): Specifies the tenant ID for which to reindex potential matches.
   • distributed (Optional): If set to true, the task runs in distributed mode. Default is false.
   • taskPartsCount (Optional): Specifies the maximum number of sub-tasks for distributed execution. Default is 2.

   • filter (Optional): Enables filtering by a condition. The format is:

     filter=(ConditionType [AND/OR ConditionType]*)
     

     Entities matching the filter will have their potential matches reindexed.

Best Practices:

• Monitor Task Progress: Use the Tasks API to monitor the status of the reindex task.
• Schedule During Off-Peak Hours: To minimize impact on system performance, schedule the reindex task during periods of low activity.
• Review Match Rules: Before reindexing, ensure that match rules are correctly configured to prevent future inconsistencies.

Additional Resources

• Potential Matches Reindex Task Documentation
• Tasks API Overview