[
https://issues.apache.org/jira/browse/PIO-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16625955#comment-16625955
]
ASF GitHub Bot commented on PIO-168:
------------------------------------
Github user EmergentOrder commented on the issue:
https://github.com/apache/predictionio/pull/466
Actually, according to the docs, existing indices, and so apps, should
continue to work in 6.X (but will be disallowed in 7.X). I assume there is a
documented ES migration process. There may be exceptions in template code, such
as in the UR where the urindex is hot-swapped. I haven't tested this, but I
will.
Assuming that existing apps keep working, and on (re)creation they work,
from the user's perspective I don't see a disruption / need for a PIO migration
tool. This obviously doesn't hold for when we get to ES 7 though.
> Elasticsearch 6.x support
> -------------------------
>
> Key: PIO-168
> URL: https://issues.apache.org/jira/browse/PIO-168
> Project: PredictionIO
> Issue Type: New Feature
> Components: Core
> Affects Versions: 0.13.0
> Reporter: Donald Szeto
> Assignee: Alexander Merritt
> Priority: Major
> Fix For: 0.14.0
>
>
> This is a JIRA ticket for tracking the pull request from [~emergentorder]
> that adds support of Elasticsearch 6.x.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
