-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
122
-
Not defined
Context:
Right now, the ElasticSearch version check has a list of versions that are supported. Once a new version of ES is released, we add that version manually to that list. In addition, we have a list of ElasticSearch versions that should throw a warning that the ElasticSearch version is officially not supported but might work. This is especially interesting if someone uses an old version of Optimize that doesn't support a newer version of ES officially. However, right now we need to add the warning versions manually, which is not necessary since all minor versions of ES after the latest officially supported version should work out of the box. For instance, Optimize 3.0.0 supports ES 7.0-7.6. The version >= 7.7 should likely work with 3.0 as well but it's not officially tested so we should throw a warning here. We can implement this behavior directly instead of adding the warning versions manually.
AT:
- the Optimize throws a warning for each ElasticSearch version that has a greater minor version than the last officially supported one.
This is the controller panel for Smart Panels app
Automatically add ElasticSearch version warning check
-
Task
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
122
-
Not defined
Context:
Right now, the ElasticSearch version check has a list of versions that are supported. Once a new version of ES is released, we add that version manually to that list. In addition, we have a list of ElasticSearch versions that should throw a warning that the ElasticSearch version is officially not supported but might work. This is especially interesting if someone uses an old version of Optimize that doesn't support a newer version of ES officially. However, right now we need to add the warning versions manually, which is not necessary since all minor versions of ES after the latest officially supported version should work out of the box. For instance, Optimize 3.0.0 supports ES 7.0-7.6. The version >= 7.7 should likely work with 3.0 as well but it's not officially tested so we should throw a warning here. We can implement this behavior directly instead of adding the warning versions manually.
AT:
- the Optimize throws a warning for each ElasticSearch version that has a greater minor version than the last officially supported one.