Merge Tree Consistency Based on Entities Task

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

This task scans the ENTITIES column family to identify and, optionally, fix inconsistencies in merge tree structures.

A tenant admin role is required to run the request.

Request

POST {ApplicationURL}/api/{tenantId}/mergeTreeConsistencyCheckForEntities

Table 1. Query Parameters
Parameter	Required	Description
`tenantId`	Yes	The identifier 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	If set to `true`, the task fixes found inconsistencies. Default: `false`.
`produceEvents`	No	If this parameter is set to `true`, the task generates events when an entity is fixed. Default is `true`.

Table 2. Body Parameters
Parameter	Required	Description
`entitiesToCheck`	No	JSON Array of entity or relation URIs to check. Default value is empty, meaning that all URIs will be checked.
`checkWinnersOnly`	No	If set to `true`, the task only scans and checks for winners. Default: `true`.

Example

Here's a simple example of a check for a couple of URIs including winners and losers:

{
"entitiesToCheck": ["URI1", "URI2"]
"checkWinnersOnly ": false
}