Accelerate the Value of Data

Relations ES Cassandra Consistency Check

Compares relationshisps in the main and search storages

This task compares entities between the main and search storages and resolves basic inconsistencies if found. If some relations are present in the search but not present in the main data storage, this task removes these relations from the search storages. If some relations are present in the main storage but not present in search, task tries to reindex such relations.

Note: Stop and Pause are supported. In case of Pause, the task restarts from the beginning.

Body

If provided, this will process the objects specified in the JSON array.

[
    "reltaions/Uri1",
    "reltaions/Uri2",
    ...
    "reltaions/UriN"
]

Requests:

Tenant admin role is required:
POST {ApplicationURL}/api/{tenantId}/potentialMatchesEsCassandraConsistencyCheck&fast=true
Note: The fast=true option is deprecated. Therefore, use the MemorySafePotentialMatchesCassandraEsConsistency task instead.
Table 1. Parameters
Parameter Required Description
tenantId Yes ID of the tenant to compare relations.
relationshipTypeNoThe relationship type to be checked. If this parameter is not specified, all relationship types will be checked.
maxResultsToStoreNoThe task stores URIs of the entities, for which inconsistency was found, in its status. This parameter is required to prevent huge consumption of memory when a large number of entities with inconsistency are found. Default value: 100.
compareVersionsNoIf set to true, then the version of the objects in the main and search storages will also be compared.. Default is false.
fixInconsistencyNoIf set to true, the task will fix inconsistencies. Default is true.
restoreTILsNoIf set to true, the task will add TIL column for relations for which it is missing. Default is false.
fixVersionConflictsNo

If the parameter is set to true, then the task will reindex relations with version conflicts in ES. Default is false.

distributedNoIf you set this parameter to true, the task will be executed in the distributed mode. By default, this is set to false.
tasksPartsCountNoThe number of tasks that will be created for distributed reindexing. Each tasks will reindex its own part of objects, which may be executed on different API nodes in parallel. We recommend you enter a value that is equal to the total count of API nodes that will execute the tasks. This field defaults to 2.
Note: Use this parameter only in the distributed mode.
largeVersionThresholdNoThe version of the threshold in which to flag objects that have a large version. All objects with a version whose threshold is more than what is specified here is reported in the objectsAboveVersionThreshold field. The total number of objects that have a version above this threshold is reported in the totalObjectsAboveVersionThreshold field. The default value is 2^60.