When you make changes in your Collibra environment—for example, when you import millions of assets—the changes are logged in a PostgreSQL database table. The changes then need to be reflected in the search index. Instead of processing these millions of changes all at once, the Search service processes them in batches or processing cycles. This process of updating a search index asynchronously in batches or processing cycles is called asynchronous indexing.
Asynchronous indexing helps ensure optimal performance of your environment while Collibra is indexing changes.
Note
- Although asynchronous indexing allows you to continue using your Collibra environment during a significant change to the environment, it may take some time to process all of the changes. For example, if you are importing millions of assets, while the changes are being processed, search results targeting the imported assets might be incomplete until the processing is complete.
- You can edit the asynchronous indexing settings.
- When a full reindex is initiated, any queued asynchronous search reindex jobs are canceled, ensuring that the full reindex proceeds without delay. Updates from the canceled jobs are included in the full reindex. Search reindex jobs that are already in progress aren't affected.
Benefits
- Fewer occasions where reindexing is necessary.
- Allows you to continue to use Collibra even after significant changes to your environment (for example, when importing millions of assets).
- Reduced memory demand when importing.
Limitations
- Importing performance could be slightly reduced.
- When processing changes, search results targeting the imported assets might be incomplete until the processing is complete.