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
Parameter	Required	Description
`tenantId`	Yes	The identifier of the tenant to check.
`distributed`	No	Runs in distributed mode if set to `true`. This means that several tasks (as specified in tasksPartsCount) will be created instead of one. Each task will reindex its own part of objects. These tasks will be executed in parallel on different API nodes (if there are more than one free API node which may execute periodic tasks). The `parallelExecution` parameter will be set to true automatically for all of these tasks in this case, therefore please make sure that no other tasks for the same tenant are running. Default: `false`.
`taskPartsCount`	No	Number of tasks which will be created for distributed reindexing, each task will reindex its own part of objects, and all of them may be executed on different API nodes in parallel. Recommended value: count of API nodes which can execute the tasks. Default value: 2. This parameter is only used in distributed mode, otherwise 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.
`checkAll`	No	Scans losers, winners, and their winners’ crosswalks to ensure all contributors are in the tree. Default: `false`.
`checkLosers`	No	Checks only losers in the merge tree. Default: `true`.
`checkWinners`	No	Checks only winners in the merge tree. Default: `true`.
`checkCrosswalks`	No	Checks 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.

Footer

You've found your way to a temporary environment. Content is not complete or final. Looking for Reltio documentation? Go to docs.reltio.com.

Unify and manage your data

Merge Tree Consistency Based on Records Task

Example

Footer