-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
AT:
- Optimize works with Elasticsearch 6.3, 6.4, 6.5
- There are Jenkins jobs running every night that tests the Elasticsearch support
- The supported Elasticsearch versions are added to the supported evnironment in the Technical guide. Also there is a warning that says: "Other Elasticsearch versions might work as well, but those are not officially supported and therefore it is strongly recommended to use one of the stated versions."
- the supported Elasticsearch versions can be read on the download page
This is the controller panel for Smart Panels app
[OPT-1771] It is nightly tested that Optimize works with the supported Elasticsearch versions
6.3.0 is incompatible when running with Java 9 (which is default jdk in the elasticsearch docker image) due a bug in the painless lang https://github.com/elastic/elasticsearch/pull/31348
Tests will run with 6.3.1
rejecting this version will be addressed with https://app.camunda.com/jira/browse/OPT-1827
https://ci.optimize.camunda.cloud/view/all/job/elasticsearch_compatibility/
The PR with the job is already merged, reviewed by Andrea.
Again a great job that you have done here! 
I also had a short look at the ci PR and a couple of remarks on that:
- Do we really need to run a nightly job for ES 6.2, since we already run the default IT against it?
- A possible improvement for the future?: Right now we have to adjust manually (in the groovy script) against which Elasticsearch versions Optimize is tested. Maybe we can define a list of Elasticsearch versions somewhere and then those jobs are created automatically from that list.
johannes.heinemann
OMG good point with 6.2, I got blind to that spot removed
https://github.com/camunda/camunda-optimize/commit/832b37a013c9e6217471883233a91aad8db9db78
The second point is a really good point, I thought about that but wasn't confident enough whether this works out with the pipeline description, but I agree that this would be a good thing to do
I added a note to https://app.camunda.com/jira/browse/OPT-1794 as I would prefer to define the list of supported version in a pom property next to the elasticsearch.test.version property
sebastian.bathke: we are not sure yet, if we really want to officially support AWS Elasticsearch. For that reason, let's wait until Felix decided on that before we create automated tests for that.