ElasticSearch and OpenSearch: Now Different Origins

Following the trend already marked when we integrated OpenDistro, we take the next natural step, integrating OpenSearch.

OpenDistro has already stopped generating new versions, moving all its developments to OpenSearch. That is why, from this version on, we also integrate with OpenSearch.

In order not to limit the number of possible sources for entities, we are going to separate the entities on ElasticSearch from those on OpenSearch.

Open

As shown in the image above, we can see that the DB instances are separated. The operation will be the same (properties, templates, etc.) but they will appear as different data sources, in case at some point it is necessary to work with both at the same time.

To configure the access to the OpenSearch instance, new properties have been created in the centralized configuration “Platform“:

Open

This also allows you to choose where you want your audit entities to be stored. To do this, you simply have to change, in the centralized configuration and the “audit” section, the field “defaultRtdbDatasource” indicating one of the values: “mongodb”, “elasticsearch” or “opensearch”.

If the creation of such audit entities fails on the selected source, they will be created by default in MongoDB.

To activate OpenSearch as a data source, you must start the modules “Control-Panel“ and ”Semantic-inf-broker” (router) with the properties “onesaitplatform.database.opensearch.enabled“ or the environment variable “OPENSEARCH_ENABLED“ as true.

Finally, the initialization process for OpenSearch has also been created in the Config-init module. To use it, you will simply have to activate it with the property “onesaitplatform.database.opensearch.enabled“ or the environment variable “OPENSEARCH_ENABLED“ to true, as for any other initial load.