[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945799#comment-15945799
]
Pat Ferrel commented on PIO-49:
-------------------------------
I've got the UR without any code changes working with ES1 but fails the
integration test because scores are wrong. This will be difficult to track
down. The ranking is the same, only scores differ in the integration test.
1) if we publish storage jars to maven then any UR user will be able to build
the Template from anywhere but I'll have to mod the `build.sbt`. to build at
all and certainly to use ES5. I think this is acceptable. The issue here is
that ES is not longer in the PIO jars, only in the Spark jars and so must be
moved to the Template lib/ dir or must be available in the maven-verse. Asking
a user to move the storage jars is not really cool but in the maven-verse no
need.
2) the score diffs I see should probably not block anything since it may be
weeks to track down.
Ship it!
> 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
> Assignee: Donald Szeto
> Priority: Blocker
> Fix For: 0.11.0
>
>
> 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.15#6346)
