archetype
>> camel-archetype-spring-boot. Camel Version 2.17.0 gets Spring Boot 1.3.3
>> After adding the camel-elasticsearch component, it requests
>>org.elasticsearch:elasticsearch:2.2.0 but Spring boot 1.3.3 forces
>>elasticsearch1.5.2 to be picked.
>>
ly work with old ES version.
>
> On Fri, Apr 22, 2016 at 11:04 AM, Lefteris Tsallas
> wrote:
>> Hi all,
>>
>> I started a new Camel Spring Boot project using the maven archetype
>> camel-archetype-spring-boot. Camel Version 2.17.0 gets Spring Boot 1.3.3
>> A
ring Boot 1.3.3
>> After adding the camel-elasticsearch component, it requests
>> org.elasticsearch:elasticsearch:2.2.0 but Spring boot 1.3.3 forces
>> elasticsearch1.5.2 to be picked.
>>
>> So If you add a route with elasticsearch component the applic
rsion 2.17.0 gets Spring Boot 1.3.3
> After adding the camel-elasticsearch component, it requests
> org.elasticsearch:elasticsearch:2.2.0 but Spring boot 1.3.3 forces
> elasticsearch1.5.2 to be picked.
>
> So If you add a route with elasticsearch component the application fails t
Hi all,
I started a new Camel Spring Boot project using the maven archetype
camel-archetype-spring-boot. Camel Version 2.17.0 gets Spring Boot 1.3.3
After adding the camel-elasticsearch component, it requests
org.elasticsearch:elasticsearch:2.2.0 but Spring boot 1.3.3 forces
Hi jakub,
Thanks for your reply. I did the same thing. Then it was working fine.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765540.html
Sent from the Camel - Users mailing list archive at Nabble.com.
wrote:
>> > Any quick suggestions will be more helpful...
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765090.html
>> > Sent from the Came
t; > Any quick suggestions will be more helpful...
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765090.html
> > Sent from the Camel - Users mailing list archive at Nabble.co
ill be more helpful...
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765090.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: c
Any quick suggestions will be more helpful...
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764662p5765090.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Thanks a lot for quick reply
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764483p5764663.html
Sent from the Camel - Users mailing list archive at Nabble.com.
-elasticsearch-component-tp5764662.html
Sent from the Camel - Users mailing list archive at Nabble.com.
ta. Is there any way
> to do this using camel elasticsearch component. I checked documentation but
> didnt find anything related to this.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/camel-elasticsearch-component-tp5764483.html
> Sent fr
I am new to camel, using elasticsearch component. I wants to write my own
query based on fields in elasticsearch and fetch the data. Is there any way
to do this using camel elasticsearch component. I checked documentation but
didnt find anything related to this.
--
View this message in context
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-elast
he 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
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-specifi
17 matches
Mail list logo