-
Bug Report
-
Resolution: Done
-
L3 - Default
-
None
-
None
-
None
-
Not defined
Context:
In Optimize 3.1.0 a new field on the dashboard index was introduced which wasn't initialised during the update from 3.0.0 to 3.1.0. While this didn't cause any issues the update from 3.2.0 to 3.3.0 assumes this field to default to an empty array in an update script ultimately causing a NPE that aborts the update from 3.2.0 to 3.3.0
AT:
- the update guide for 3.2.0 to 3.3.0 is extended with this known issue and a workaround (curl to intialize the field and then resuming the update
- the doc branches master, latest & 3.3.0 are updated accordingly