Unify and manage your data

Merge Tree Consistency Based on Records Task

Learn about the task to check and fix merge tree inconsistencies in the ENTITIES_MERGE_TREE column family.

This task scans the ENTITIES_MERGE_TREE column family to identify and, optionally, fix inconsistencies in merge tree structures, such as phantoms in losers.

A tenant admin role is required to run the request.

Request

POST {ApplicationURL}/api/{tenantId}/mergeTreeConsistencyCheckForRecords
Table 1. Path and Query Parameters
ParameterRequiredDescription
tenantIdYesThe identifier of the tenant to check.
distributedNo
If set to true, the task runs in distributed mode. Default value is false. For more information, see Distributed mode.
taskPartsCountNo
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.
fixInconsistencyNoIf set to true, the task fixes found inconsistencies.

Default: false.

produceEventsNoIf this parameter is set to true, the task generates events when an entity is fixed.

Default is true.

Table 2. Body Parameters
ParameterRequiredDescription
entitiesToCheckNoJSON Array of entity or relation URIs to check.

Default value is empty, meaning that all URIs will be checked.

checkAllNoScans losers, winners, and their winners’ crosswalks to ensure all contributors are in the tree.

Default: false.

checkLosersNoChecks only losers in the merge tree.

Default: true.

checkWinnersNoChecks only winners in the merge tree.

Default: true.

checkCrosswalksNoChecks winners and their crosswalks to ensure all contributors are in the tree.

Default: false.

Example

Here's a simple example of a check for two specific URIs, scanning winners, losers, and crosswalks:
 {
    "entitiesToCheck": ["URI1", "URI2"],
    "checkAll": true
} 
Note: When checkAll is true, the other check parameters are ignored.