[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833120#comment-15833120
]
ASF GitHub Bot commented on PIO-49:
-----------------------------------
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
1) The effect on PIO. IMO ES 1.x should be the default build requiring no
config change anywhere. We should somehow mark ES 1.x as "being deprecated" for
a release or 2 and support 5.x with new config. Over time ES 5.x becomes the
default and es 1.x becomes truly removed to keep old cruft to a minimum.
2) The effect on Templates. This seems problematic since few of the
Templates are actually part of what the PIO team maintains. Personally I'm for
making some fairly radical changes but they should be done IMO all at once in a
primary version change like 0.x to 1.x. Until then we risk most of the
Templates becoming dead-end zombies. Too many haven't even been moved to the
new namespace.
I agree that in all likelihood only the UR will need a code change to
support 5.x and am willing to commit to that as long as the other Templates
remain untouched--ideally.
My $0.02 worth
> Add support for Elasticsearch 5.x
> ---------------------------------
>
> Key: PIO-49
> URL: https://issues.apache.org/jira/browse/PIO-49
> Project: PredictionIO
> Issue Type: Improvement
> Reporter: Shinsuke Sugaya
>
> We work on meta/event storage support for Elasticsearch 5.x.
> Although Elasticsearch 2.x does not allow dots in field names,
> Elasticsearch 5.x supports it. So, it's better to upgrade to ES 5.x release.
> Since ES 5.x provides Java Rest API client, we replaced
> Transport communication with HTTP one. Therefore, our fix
> uses HTTP(9200 port) only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
