-
Task
-
Resolution: Unresolved
-
L3 - Default
-
None
-
None
-
None
-
None
-
Not defined
Do the OpenSearch implementation for the entities operations
Testing notes
Implemented TenantReaderOs and TenantWriterOs should be called in the tab Collection in the app with os db profile. The content of these records should be the same as we have while launching the app with es db profile.
To make this process easier I would advice to set up the chrome extension Multi Elasticsearch Head and connect to the elasticsearch(9200 port) and opensearch(9205 port) after launching the app 2 times with the different db profiles. Then find the tab "Browse" and open indices to see the content of them. Then compare.
To launch the app you have to with opensearch db profile:
- Run
docker-compose -f docker-compose.yml --profile opensearch up -d
- Start Optimize with
SPRING_PROFILES_ACTIVE=opensearch
- The startup will fail and that's ok, BUT...
- Check that all indexes were created in opensearch
- Then go to the tab with chrome extension
This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10021. Please use this link for any future references and continue any discussion there.