[ 
https://issues.apache.org/jira/browse/PIO-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15877901#comment-15877901
 ] 

ASF GitHub Bot commented on PIO-49:
-----------------------------------

Github user marevol commented on the issue:

    https://github.com/apache/incubator-predictionio/pull/336
  
    To solve this issue, how about using plugin directory?
    In our branch(https://github.com/jpioug/incubator-predictionio), ES1/ES5 
codes in data were extracted to data-elasticsearch and data-elasticsearch1 
project. Putting the jar file into plugin directory, it works.
    So, default PIO distribution contains pio-data-elasticsearch5.jar in 
plugins directory,
    and then if you want to use ES1, replacing it with 
pio-data-elasticsearch1.jar, PIO works with ES1.
    I think that Plugin mechanism can keep previous behavior for 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)

Reply via email to