[
https://issues.apache.org/jira/browse/UNOMI-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17610234#comment-17610234
]
David Griffon commented on UNOMI-150:
-------------------------------------
fixed by related commits
https://github.com/apache/unomi/search?q=UNOMI-150&type=commits
if the issue is not complete, please create a new one with a specific
description
> 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: unomi(-core)
> Affects Versions: unomi-1.3.0-incubating
> Reporter: Jarek Lipski
> Priority: Major
> Fix For: unomi-2.0.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
(v8.20.10#820010)
