[
https://issues.apache.org/jira/browse/PIO-172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16740108#comment-16740108
]
Takako Shimamoto commented on PIO-172:
--------------------------------------
Users can choose Elasticsearch for EVENTDATA.
I guess it's almost impossible to provide a migration tool because an
Elasticsearch cluster which is made up of a number of nodes in production
probably has various configuration settings and complex cluster topologies. I
think it's not that easy to resolve this change with the tool. As far as I'm
concerned, it's realistic to provide just a guide which explains how to migrate
current indexes by reindexing.
like this,
https://www.elastic.co/guide/en/elasticsearch/reference/6.0/reindex-upgrade-inplace.html
I'm checking the reindex process now.
> 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)
