Reindexing the Unmapped Values
This task enables you to reindex the unmapped values in a tenant.
Important: You must run this task if any data synchronization issues are detected.
To reindex the unmapped values, use the parameters listed in Table 1: Parameters to Reindex Unmapped Values.
| Parameter Name | Mandatory | Type | Description |
|---|---|---|---|
type
| No | String | Defines the lookup type of unmapped values to reindex. If this parameter is not set then all unmapped values will be reindexed. |
uris
| No | Array | Defines the list of unmapped URIs that are to be reindexed. |
enableSeparateIndexing | No | Boolean | If set to true, unmapped values will reindex into a separate index. If not set, unmapped values will be reindexed into the existing index. For more information, see About enableSeparateIndexing. |
Example: Reindexes all unmapped values in a tenant
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "reindexUnmapped"
}
Example: Reindex unmapped values of a specific lookup type
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "reindexUnmapped",
"parameters": {
"type": "rdm/lookupTypes/Country"
}
}
Example: Reindex unmapped values by specific URIs
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "reindexUnmapped",
"parameters": {
"uris": [
"rdm_tenant_id/Country/Reltio/CA",
"rdm_tenant_id/Country/AHA/USA",
"rdm_tenant_id/Country/HMS/CZ"
]
}
}
Example: Reindex unmapped values using separate indexing
POST https://{{rdm-service}}/tasks/{{tenantId}}
Authorization: Bearer {{token}}
{
"type": "reindexUnmapped",
"parameters": {
"enableSeparateIndexing": "true"
}
}About enableSeparateIndexing
When the reindex task runs with enableSeparateIndexing=true, the system creates a second index called the bufferedIndex. During the task:
- Your tenant temporarily maintains two indexes: the main index and the buffered index.
- The API continues to use the main index for searches, while writing updates to both indexes.
- This setup allows reindexing to occur in the background, without disrupting your work.
After the task completes, the system promotes the buffered index to replace the main index. All unmapped values are stored in a single index, and the old index is discarded.
Attention: Use this parameter only when reindexing the entire tenant. If you apply it to a subset (such as a specific type or a set of URIs), the remaining Elasticsearch data will be lost.
While the task is running, you can continue working without needing to wait for it to finish.