Unify and manage your data

Cassandra Matches Consistency Task

This task compares entities and matches in the main storage.

This task compares two parts of the main storage: entities and matches in the background. It may resolve basic inconsistencies if found. If some entities are present in matches but not present in the entities data storage, this task removes these entities from the matches. If some entities are present in both parts but have different versions, this task rebuilds matches for such entities.

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

Requests:

Tenant admin role is required:

POST {ApplicationURL}/api/{tenantId}/matchCassandraConsistencyCheck&fast=true
Note: The fast=true option is deprecated. Therefore, use the MemorySafeCassandraMatchesConsistency task instead.
Table 1. Parameters
Parameter Required Description
tenantId Yes ID of the tenant to compare matches and entities.
entityType No The entity type to be checked (all types will be checked if this parameter is absent).
maxResultsToStore No The 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.
compareVersions No If set to true, then the version of the objects in the entities and matches will also be compared.. Default is false.
fixInconsistency No If set to true, the task will fix inconsistencies. Default is true.
fixVersionConflicts No

If the parameter is set to true, then the task will also rebuild matches for the entities with version conflicts. Default is false.

Body (optional)

The JSON array of entity URIs to be check and fix inconsistencies.