Loading...

XML

Word

Printable

AT:

after upgrading Optimize from one minor version to the next:
- the data from the old version is still available
- Optimize is fully running as I would just use the newest version without the upgrade
- changes in the data structure are updated as well
During the jar execution:
- if the upgrade jar is not executed from the upgrade folder, I see a designated error message
- If Elasticsearch is not running I see a designated error message
- If current Elasticsearch data structure version does not correspond to the upgrade version of the jar, I see a dedicated error message.
I can read documentation about how to upgrade Optimize
Optimize is tested the following ways:
- Deploy old schema version. Perform update script. Run normal integration tests
- Deploy old schema. Add data (e.g. 100 000 process instances). Perform update script. import all data and check that everything is imported and the new fields have values as expected.
- Unit tests that ensure the elasticsearch upgrade Operations perform as expected.

1.	I can update schema automatically	Done	Unassigned
2.	I can start upgrade process from CLI	Done	Unassigned
3.	Add elasticsearch http port to configuration	Done	Unassigned
4.	I can read documentation on upgrade for developers	Done	Unassigned
5.	I can read documentation on upgrade execution and configuration	Done	Unassigned
6.	As a user I can adjust the logging level of the upgrade jar	Done	Unassigned
7.	Change start-up script setup	Done	Unassigned
8.	I can run the integration tests on an upgraded optimize	Done	Unassigned
9.	I can test that the optimize upgrade works on large data	Done	Unassigned
10.	Use json path to define adjustments within the upgrade steps	Done	Unassigned
11.	I see a warning before I can upgrade Optimize	Done	Unassigned