[
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879255#comment-15879255
]
ASF GitHub Bot commented on PIO-49:
-----------------------------------
Github user marevol commented on the issue:
https://github.com/apache/incubator-predictionio/pull/336
Please see our snapshot build:
http://fess.codelibs.org/snapshot/apache-predictionio-0.11.0-v1-SNAPSHOT.zip
Storage implementations, such as hbase, were moved to plugins/data-*
projects,
and jar files are put to plugins directory in the distribution.
IMO, I think that Plugin is better than maven profile.
As for plugin, PIO user can select features in 1 distribution without
building PIO,
and also add own storage implementation they want.
In our build, if you want to use ES1, (I'm working on this issue now. For
ES1, more testing might be need...)
1. Remove plugins/pio-data-elasticsearch-assembly-0.11.0-v1-SNAPSHOT.jar
2. Move extra/pio-data-elasticsearch1-assembly-0.11.0-v1-SNAPSHOT.jar to
plugins/
3. Modify conf/pio-env.sh (you can use previous ES1 settings)
4. Start PIO (That's all!)
Although I did not check it on UR template, it may work with no
modification(or dependencies update) with ES1.
> 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)
