You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by Andrea Cosentino <an...@yahoo.com.INVALID> on 2017/12/19 13:42:41 UTC
Elasticsearch5 components and Elasticsearch 6.x
Hello,
Currently we have two components: Elasticsearch5 that will be deprecated and Elasticsearch5Rest that will be the main component, since it will use the ES rest client, suggested from Elasticsearch community.
ES 6 is already released and we have also the bundles for that.
Do we need to change the name of Elasticsearch5Rest to ElasticsearchRest and upgrade to 6.x?
I believe this is something we should try to accomplish before 2.21.0 release.
Thanks.
--Andrea Cosentino ----------------------------------Apache Camel PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
Re: Elasticsearch5 components and Elasticsearch 6.x
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
+1 as well.
Regards
JB
On Dec 19, 2017, 19:34, at 19:34, Francois Papon <fr...@openobject.fr> wrote:
>Hi,
>
>As a Camel user, I agree about rename this component without version
>number because actually we have to change camel route endpoint to
>upgrade ES component.
>
>+1
>
>François
>
>
>Le 19/12/2017 à 19:30, Zoran Regvart a écrit :
>> Sounds very reasonable to me we should name it so it doesn't look
>outdated.
>>
>> We already had a couple of component renames in 2.20 (CAMEL-11242 and
>> CAMEL-11575 come to mind) and there hasn't been any uproar from the
>> community.
>>
>> So +1
>>
>> zoran
>>
>> On Tue, Dec 19, 2017 at 2:42 PM, Andrea Cosentino
>> <an...@yahoo.com.invalid> wrote:
>>> Hello,
>>> Currently we have two components: Elasticsearch5 that will be
>deprecated and Elasticsearch5Rest that will be the main component,
>since it will use the ES rest client, suggested from Elasticsearch
>community.
>>> ES 6 is already released and we have also the bundles for that.
>>> Do we need to change the name of Elasticsearch5Rest to
>ElasticsearchRest and upgrade to 6.x?
>>> I believe this is something we should try to accomplish before
>2.21.0 release.
>>> Thanks.
>>> --Andrea Cosentino ----------------------------------Apache Camel
>PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail:
>ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
>>
>>
Re: Elasticsearch5 components and Elasticsearch 6.x
Posted by Francois Papon <fr...@openobject.fr>.
Hi,
As a Camel user, I agree about rename this component without version
number because actually we have to change camel route endpoint to
upgrade ES component.
+1
François
Le 19/12/2017 à 19:30, Zoran Regvart a écrit :
> Sounds very reasonable to me we should name it so it doesn't look outdated.
>
> We already had a couple of component renames in 2.20 (CAMEL-11242 and
> CAMEL-11575 come to mind) and there hasn't been any uproar from the
> community.
>
> So +1
>
> zoran
>
> On Tue, Dec 19, 2017 at 2:42 PM, Andrea Cosentino
> <an...@yahoo.com.invalid> wrote:
>> Hello,
>> Currently we have two components: Elasticsearch5 that will be deprecated and Elasticsearch5Rest that will be the main component, since it will use the ES rest client, suggested from Elasticsearch community.
>> ES 6 is already released and we have also the bundles for that.
>> Do we need to change the name of Elasticsearch5Rest to ElasticsearchRest and upgrade to 6.x?
>> I believe this is something we should try to accomplish before 2.21.0 release.
>> Thanks.
>> --Andrea Cosentino ----------------------------------Apache Camel PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
>
>
Re: Elasticsearch5 components and Elasticsearch 6.x
Posted by Zoran Regvart <zo...@regvart.com>.
Sounds very reasonable to me we should name it so it doesn't look outdated.
We already had a couple of component renames in 2.20 (CAMEL-11242 and
CAMEL-11575 come to mind) and there hasn't been any uproar from the
community.
So +1
zoran
On Tue, Dec 19, 2017 at 2:42 PM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> Hello,
> Currently we have two components: Elasticsearch5 that will be deprecated and Elasticsearch5Rest that will be the main component, since it will use the ES rest client, suggested from Elasticsearch community.
> ES 6 is already released and we have also the bundles for that.
> Do we need to change the name of Elasticsearch5Rest to ElasticsearchRest and upgrade to 6.x?
> I believe this is something we should try to accomplish before 2.21.0 release.
> Thanks.
> --Andrea Cosentino ----------------------------------Apache Camel PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
--
Zoran Regvart
Re: Elasticsearch5 components and Elasticsearch 6.x
Posted by Claus Ibsen <cl...@gmail.com>.
+1
On Tue, Dec 19, 2017 at 2:42 PM, Andrea Cosentino
<an...@yahoo.com.invalid> wrote:
> Hello,
> Currently we have two components: Elasticsearch5 that will be deprecated and Elasticsearch5Rest that will be the main component, since it will use the ES rest client, suggested from Elasticsearch community.
> ES 6 is already released and we have also the bundles for that.
> Do we need to change the name of Elasticsearch5Rest to ElasticsearchRest and upgrade to 6.x?
> I believe this is something we should try to accomplish before 2.21.0 release.
> Thanks.
> --Andrea Cosentino ----------------------------------Apache Camel PMC MemberApache Karaf CommitterApache Servicemix PMC MemberEmail: ancosen1985@yahoo.comTwitter: @oscerd2Github: oscerd
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2