Potential Matches Reindex Task
Information about how to reindex potential matches.
This task contains the following steps:
PotentialMatchesRemoveTask- This task cleans old potential matches information in the tenant index.PotentialMatchesReindexTask- This task reindexes the potential matches information from scratch by using the match tables.
You must run this task if inconsistencies are detected in the potential matches counters.
Stop and Pause actions are supported.
Requests
Administrator role is required:
POST {ApplicationURL}/rebuildpmcountersTenant admin role is required:
POST {ApplicationURL}/api/{tenantId}/rebuildpmcounters| Parameter | Required | Description |
|---|---|---|
tenantId
| Yes | ID of the tenant to reindex potential matches. |
distributed | No |
If set to
true, the task runs in distributed mode. Default value is false. For more information, see Distributed mode. |
taskPartsCount | No |
Specifies the maximum number of sub-tasks for distributed execution. The platform determines the optimal number based on performance limits. Default value is
2. Note: This parameter is only applicable when distributed=true. Otherwise, it s ignored. |
filter | No | Enables filtering by a condition. The format for the filter query parameter is as follows: If an entity matches the filter, then its potential matches are reindexed |