Open a JIRA and submit your patch.
On Mon, Jun 2, 2014 at 8:25 AM, nocturnal3d <nocturna...@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
