Fix Incomplete Merge Task
This task checks (based on some internal data and logic) if any entities appear as losers but are not completely merged.
Such entities are fixed if the merge can be completed; otherwise, the task sends a notice about such cases.
Stop and Pause are supported.
Requests
Tenant admin role is required:
POST {ApplicationURL}/incompleteMergesCheckTenant admin role is required:
POST {ApplicationURL}/api/{tenantId}/incompleteMergesCheck| Parameter | Required | Description |
|---|---|---|
tenantId | Yes | ID of the tenant to check. |
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. |
fixInconsistency | No |
The task does not fix a found inconsistency if this parameter is set to Default is |
force | No |
If set to Default is Note: If you use this parameter, you must use it carefully, since it may cause unexpected results. Before running the task forcefully, you must run the task with the
fixInconsistency parameter disabled, and you must manually verify all found potential incomplete merge operations. |
checkSince | No | Timestamp in UNIX format. If this parameter is specified, then only entities merged after the timestamp are checked. |
maxResultsToStore | No |
This parameter stores incomplete merge operations found in the format Default value is |
Body (optional)
JSON Array of entity and/or relation URIs to be checked.