Reltio Support
Knowledge Base
Match/Merge

Potential Matches Reindex Task

Shantanu Indra

Updated May 26, 2021 10:45

Problem

How to resolve inconsistencies in potential matches counter?

Solution

As an initial step, post investigating an issue with potential matches related to inconsistencies in the data, the potential matches reindex task can be run to fix the potential matches inconsistencies.

This task cleans potential matches information in the ES, Elastic Search, and reindexes it from scratch by using match tables.

Stop and Pause are supported.

Requests

Admin role is required:

POST {ApplicationURL}/rebuildpmcounters

Tenant admin role is required:

POST {ApplicationURL}/api/{tenantId}/rebuildpmcounters


Parameter	Required	Description
`tenantId`	Yes	ID of the tenant to reindex potential matches.

Comments

0 comments

Please sign in to leave a comment.

Articles in this section

How can we configure multiple match rules in the already existing proximity match entity?
Will the entities retain the same Entity ID/Reltio ID after an Unmerge?
Match rule cleanser doesn't cleanse some characters, although they present in the dictionary. Why?
[Video] How can a platform reset Not-a-Match and Manual-Match Flags
Potential Matches Reindex Task
Best practices after changing match rules?
What is proximity fuzzy matching and how can I enable it?
Why aren't we seeing a match for FirstName in verify matches API.
Is there any way to use a reference attribute in a match rule?
Why does ignoreInToken is set to true in verifyMatches but the attribute is not in the ignoreInToken section?