[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15885011#comment-15885011
]
ASF GitHub Bot commented on PIO-49:
-----------------------------------
Github user pferrel commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
@dszeto I meant `lib` = unmanaged, mistyped.
This still sounds good.
What will populate `lib/spark`? Maybe a flag in some sbt file or can a
param be passed through `pio build`? If the later we have the equivalent of a
maven build profile, sorta ad hoc but all good. The default for 0.11 is ES1,
with a param for ES5.
@marevol this means the params in pio-env.sh do not need to flag ES5, there
should be only ELASTICSEARCH and it applies to whichever is in `lib/spark` and
installed right?
> 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.15#6346)
