-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
The purpose of this ticket is to have an OptimizeOpensearchclient that is able to OpenSearch and rudimentarily communicate with it.
Refactor at least these files:
| ./util/optimize-commons/src/main/java/org/camunda/optimize/service/es/OptimizeElasticsearchClient.java |
| ./backend/src/main/java/org/camunda/optimize/service/util/ESVersionChecker.java |
| ./backend/src/main/java/org/camunda/optimize/service/es/OptimizeElasticsearchClientFactory.java |
| ./util/optimize-commons/src/main/java/org/camunda/optimize/upgrade/es/ElasticsearchHighLevelRestClientBuilder.java |
Testing notes
Please note that the PR attached to this ticket is implementing this plus 2 tickets additionally (OPT-7195, OPT-7197), since it made sense to develop the all together. So the testing notes are meant for a combined test of the requirements of the 3 tickets together.
- Start Optimize as normal in all 3 modes. The Optimize instance should default to the ElasticSearch profile and everything should be working as usual
- Shut down Optimize and start it now with SPRING_PROFILES_ACTIVE=opensearch
- Optimize will shut down with an error, since there are many things that are not implemented, but the logfiles shall have a message "OpenSearch cluster successfully started". This means that the OpenSearchclient was instantiated correctly and also that a connection was successfully established - this is the goal of this ticket