Unify and manage your data

Relations ES Cassandra Consistency Check

Compares relationships 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 the search, then the 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.

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

Requests:

Tenant admin role is required:
POST {ApplicationURL}/api/{tenantId}/relationsEsCassandraConsistencyCheck
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.

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.
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.