You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@unomi.apache.org by "Kevan Jahanshahi (Jira)" <ji...@apache.org> on 2022/08/10 15:09:00 UTC

[jira] [Assigned] (UNOMI-627) Persist migration status, and recover in case of failure

     [ https://issues.apache.org/jira/browse/UNOMI-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kevan Jahanshahi reassigned UNOMI-627:
--------------------------------------

    Assignee: Kevan Jahanshahi

> Persist migration status, and recover in case of failure
> --------------------------------------------------------
>
>                 Key: UNOMI-627
>                 URL: https://issues.apache.org/jira/browse/UNOMI-627
>             Project: Apache Unomi
>          Issue Type: Improvement
>    Affects Versions: 2.0.0
>            Reporter: Kevan Jahanshahi
>            Assignee: Kevan Jahanshahi
>            Priority: Major
>
> In case a migration script fail because ES connection close or ES out of memory or any reason.
> IT could be great to have this options:
>  * rollback ?
>  * being able to start back from the failure.
>  * having clear info on current state when a script failed.
> the main idea is to bring more robustness to current migration system.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)