You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Andrea Cosentino (JIRA)" <ji...@apache.org> on 2015/09/07 12:04:46 UTC

[jira] [Issue Comment Deleted] (CAMEL-9080) Update to elsaticsearch 1.7.1

     [ https://issues.apache.org/jira/browse/CAMEL-9080?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrea Cosentino updated CAMEL-9080:
------------------------------------
    Comment: was deleted

(was: Hi Claus,

I was waiting for James Netherton on the following ticket:

https://issues.apache.org/jira/browse/CAMEL-9080

I think we can add a link to this one.)

> Update to elsaticsearch 1.7.1
> -----------------------------
>
>                 Key: CAMEL-9080
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9080
>             Project: Camel
>          Issue Type: Task
>          Components: camel-elasticsearch
>            Reporter: James Netherton
>             Fix For: 2.16.0
>
>
> It'd be good to bump Elasticsearch to the latest 1.7.1 version. This would also necessitate a Lucene upgrade to 4.10.4.
> I think this impacts:
> camel-lucene
> camel-solr (for tests)
> camel-jcr looks to be fixed at 3.x for jackrabbit, so I presume this can stay as is?
> I saw that CAMEL-8605 proposed upgrading to Lucene 5.x. If we want Lucene version alignment across components, I think 4.10.4 is the best we can do for now.
>   
>   



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)