[
https://issues.apache.org/jira/browse/PIO-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16675284#comment-16675284
]
saurabh gulati commented on PIO-172:
------------------------------------
[~dszeto] Hey Donald, Sorry for getting back late to it. I spend some time in
understanding this issue but I am not sure what type of migration script are we
targeting.
Do we migrate all the collections that we create for PIO users in elastic?
Do we want to implement _reindex api povided by elastic and migrate all those
collections which use multiple mappings in the same index?
I tried to check the code base to figure out if we are putting multiple
mappings in a single index but couldn't find it. I could see we were creating
several indexes in elastic with single mappings.
Can you point me in the right direction.
Thanks
> Migration tool for ES 6.x changes
> ---------------------------------
>
> Key: PIO-172
> URL: https://issues.apache.org/jira/browse/PIO-172
> Project: PredictionIO
> Issue Type: New Feature
> Components: Core
> Reporter: Donald Szeto
> Assignee: saurabh gulati
> Priority: Major
>
> With PIO-168, the metadata model of ES 6.x will change to reflect
> [changes|https://www.elastic.co/guide/en/elasticsearch/reference/6.x/removal-of-types.html]
> that will become effective with ES 7.x and onward. A migration tool should
> be provided for users who want to upgrade to the latest version of PIO with
> ES, and keeping metadata intact.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
