Search service
Architecture
The Search service is built on Elasticsearch and is configured and maintained by Collibra Console and an agent.
Data storage
The data of the Search service is located in:
- Linux with root permission: /opt/collibra_data/search
- Linux without root permission: ~/collibra_data/search
- Windows: C:\collibra_data\search
It contains the following subfolders:
| Directory name | Content |
|---|---|
|
config |
The configuration of the Search service. |
| logs | All the log files created by the Search service. |
| data |
The actual search database. |
|
tmp |
The directory where the service saves its temporary files. |
Synchronization with the database
The Search service is mandatory for every Collibra environment, and generally speaking, the Search service has to be synchronized with the database in order for you to search for and work with Collibra resources. In several situations, for example after editing search or hyperlink settings or upgrading your Collibra environment, you have to synchronize the Search service with the database. Synchronization is achieved by reindexing Collibra.
If, by chance, the Search service is incorrectly configured or becomes unavailable, a Search engine unavailable warning is shown, but Collibra will still continue to function.
Users can still create, edit and delete resources; however, such activity will result in an asynchronous state between the Search service and the database. When the Search service becomes available again, if no resources were created, edited or deleted, there is no need to reindex Collibra. If, however, such changes were made in the environment, a full reindex is necessary. Your Collibra administrator is notified via a warning, as shown in the following image.
