[
https://issues.apache.org/jira/browse/UNOMI-849?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Serge Huber updated UNOMI-849:
------------------------------
Fix Version/s: unomi-3.2.0
(was: unomi-2.7.0)
> Improve Unomi migration procedure by automatically executing migration scripts
> ------------------------------------------------------------------------------
>
> Key: UNOMI-849
> URL: https://issues.apache.org/jira/browse/UNOMI-849
> Project: Apache Unomi
> Issue Type: Improvement
> Reporter: Francois Gerthoffert
> Priority: Major
> Fix For: unomi-3.2.0
>
>
> When datamodel changes are present between versions of unomi, migration
> script are present to handle the transformation.
> These scripts have to be launched manually (using unomi:migrate) during the
> migration procedure. They must be launched on one single unomi node while all
> the other nodes are shut down.
> We're in a situation where an upgrade is simple when there are no data model
> changes, but more tedious when changes are present.
> Since we do not automatically know when such migration scripts need to be
> executed, it is prone to error as we either have to remember to indicate this
> in the changelog notes, or to request the migration to always be executed
> even when not required to make sure it is not forgotten.
> This ticket aims to improve the migration procedure by having the necessary
> migration scripts executed automatically when starting a newer version of
> Unomi.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
