You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by nocturnal3d <no...@gmail.com> on 2014/06/02 17:25:11 UTC
camel-elasticsearch component starts up an instance even though IP
specified
Hi guys,
I'm using camel 2.13 with the ElasticSearch component
(camel-elasticsearch-2.13).
I specify the endpoint as such:
*elasticsearch://clusterName?operation=INDEX&indexName=indexname&indexType=doctype&ip=127.0.0.1*
I would have assumed that by specifying the IP address of the ES instance
that the component would not spool up it's own local instance - but, it
does.
I have looked at the source code and made the following changes in
ElasticsearchEndpoint.java (which seem to work - i.e. component won't spool
up an ES instance if an IP is provided):
FROM:
TO:
This seems to work. Is this a valid bug? or was the intention to spool up
the ES instance no matter what is specified?
thanks in advance. Jose.
--
View this message in context: http://camel.465427.n5.nabble.com/camel-elasticsearch-component-starts-up-an-instance-even-though-IP-specified-tp5751825.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: camel-elasticsearch component starts up an instance even though
IP specified
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I logged a ticket to not forget about it
https://issues.apache.org/jira/browse/CAMEL-7502
Jose, you are welcome to work on patch to submit
http://camel.apache.org/contributing.html
On Wed, Jun 4, 2014 at 3:42 AM, Christian Posta
<ch...@gmail.com> wrote:
> Open a JIRA and submit your patch.
>
>
> On Mon, Jun 2, 2014 at 8:25 AM, nocturnal3d <no...@gmail.com> wrote:
>
>> Hi guys,
>>
>> I'm using camel 2.13 with the ElasticSearch component
>> (camel-elasticsearch-2.13).
>>
>> I specify the endpoint as such:
>>
>>
>> *elasticsearch://clusterName?operation=INDEX&indexName=indexname&indexType=doctype&ip=127.0.0.1*
>>
>> I would have assumed that by specifying the IP address of the ES instance
>> that the component would not spool up it's own local instance - but, it
>> does.
>>
>> I have looked at the source code and made the following changes in
>> ElasticsearchEndpoint.java (which seem to work - i.e. component won't spool
>> up an ES instance if an IP is provided):
>>
>> FROM:
>>
>>
>> TO:
>>
>>
>>
>> This seems to work. Is this a valid bug? or was the intention to spool up
>> the ES instance no matter what is specified?
>>
>> thanks in advance. Jose.
>>
>>
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-starts-up-an-instance-even-though-IP-specified-tp5751825.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>
>
>
> --
> *Christian Posta*
> http://www.christianposta.com/blog
> twitter: @christianposta
--
Claus Ibsen
-----------------
Red Hat, Inc.
Email: cibsen@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: camel-elasticsearch component starts up an instance even though
IP specified
Posted by Christian Posta <ch...@gmail.com>.
Open a JIRA and submit your patch.
On Mon, Jun 2, 2014 at 8:25 AM, nocturnal3d <no...@gmail.com> wrote:
> Hi guys,
>
> I'm using camel 2.13 with the ElasticSearch component
> (camel-elasticsearch-2.13).
>
> I specify the endpoint as such:
>
>
> *elasticsearch://clusterName?operation=INDEX&indexName=indexname&indexType=doctype&ip=127.0.0.1*
>
> I would have assumed that by specifying the IP address of the ES instance
> that the component would not spool up it's own local instance - but, it
> does.
>
> I have looked at the source code and made the following changes in
> ElasticsearchEndpoint.java (which seem to work - i.e. component won't spool
> up an ES instance if an IP is provided):
>
> FROM:
>
>
> TO:
>
>
>
> This seems to work. Is this a valid bug? or was the intention to spool up
> the ES instance no matter what is specified?
>
> thanks in advance. Jose.
>
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-starts-up-an-instance-even-though-IP-specified-tp5751825.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
*Christian Posta*
http://www.christianposta.com/blog
twitter: @christianposta