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/18 14:53:00 UTC

[jira] [Resolved] (UNOMI-640) Implement safer way of retrieving the index config during the migration

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

Kevan Jahanshahi resolved UNOMI-640.
------------------------------------
    Resolution: Fixed

> Implement safer way of retrieving the index config during the migration
> -----------------------------------------------------------------------
>
>                 Key: UNOMI-640
>                 URL: https://issues.apache.org/jira/browse/UNOMI-640
>             Project: Apache Unomi
>          Issue Type: Bug
>    Affects Versions: 2.0.0
>            Reporter: Kevan Jahanshahi
>            Assignee: Kevan Jahanshahi
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently the migration is trusting the other existing indices to be correctly configured to get the conf like: number of shards, number of replicas, etc while it need to rebuild some of the indices.
> We could change that to a safer implem by just reading the available configuration regarding those properties. This way even if an index already exists with bad configuration it will not fail the migration process.



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