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

Posted to dev@unomi.apache.org by "Serge Huber (JIRA)" <ji...@apache.org> on 2019/05/15 17:56:00 UTC

[jira] [Updated] (UNOMI-150) Old index template is not deleted when migrating from 1.2.0

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

Serge Huber updated UNOMI-150:
------------------------------
    Fix Version/s: 1.5.0

> Old index template is not deleted when migrating from 1.2.0
> -----------------------------------------------------------
>
>                 Key: UNOMI-150
>                 URL: https://issues.apache.org/jira/browse/UNOMI-150
>             Project: Apache Unomi
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.3.0-incubating
>            Reporter: Jarek Lipski
>            Priority: Major
>             Fix For: 1.5.0
>
>
> When migrating from Unomi 1.2.0 to Unomi 1.3.0-SNAPSHOT, a new index template is created in Elasticsearch - "context-monthly-indices". However, old one "context_monthlyindex" remains there. Since both index templates match the same monthly index name pattern, the old template is applied.
> The solutions I propose is to delete the old "context_monthlyindex" index template via a migration script.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)