Re: Camel 2.12 : MongoDB - pre-existing indexes being dropped when using "dynamicity"

[mads64738 <ma...@yakatak.com>]

Hi Willem,

Many thanks for your reply - apologies for the delay of this response.

Unfortunately, Camel appears to throw an error on startup if the collection
is missing, hence setting it to a dummy value.

As we were using the "dynamicity" flag for reuse of routes, given that we
know the target collection(s) in use, we taken an alternative approach.  We
now lookup the route (from the configuration) and use the recipientList
construct, so that we can 'dynamically' invoke the route.

Best regards, Madhu.


Willem.Jiang wrote
> Hi,
> 
> If you don’t know the collection, can you just skip the setting of
> collection?
> 
> --  
> Willem Jiang
> 
> Red Hat, Inc.
> Web: http://www.redhat.com
> Blog: http://willemjiang.blogspot.com(http://willemjiang.blogspot.com/)
> (English)
> http://jnn.iteye.com(http://jnn.javaeye.com/) (Chinese)
> Twitter: willemjiang  
> Weibo: 姜宁willem





--
View this message in context: http://camel.465427.n5.nabble.com/Camel-2-12-MongoDB-pre-existing-indexes-being-dropped-when-using-dynamicity-tp5746575p5747598.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel 2.12 : MongoDB - pre-existing indexes being dropped when using "dynamicity"

[Mark Webb <el...@gmail.com>]

I experienced this in 2.13.2 FWIW..


On Sat, Feb 14, 2015 at 4:43 AM, Sufod <Su...@gmail.com> wrote:

> Hello,
>
> This is still happening on camel 2.14.1.
>
> Using "dynamicity=true" on MongoDb endpoint is running a dropIndexes on the
> specified collection (CamelMongoDbCollection header), for each exchange
> going through.
>
> Is this a known bug ?
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-2-12-MongoDB-pre-existing-indexes-being-dropped-when-using-dynamicity-tp5746575p5762718.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Re: Camel 2.12 : MongoDB - pre-existing indexes being dropped when using "dynamicity"

[Sufod <Su...@gmail.com>]

Hello,

This is still happening on camel 2.14.1.

Using "dynamicity=true" on MongoDb endpoint is running a dropIndexes on the
specified collection (CamelMongoDbCollection header), for each exchange
going through.

Is this a known bug ?



--
View this message in context: http://camel.465427.n5.nabble.com/Camel-2-12-MongoDB-pre-existing-indexes-being-dropped-when-using-dynamicity-tp5746575p5762718.html
Sent from the Camel - Users mailing list archive at Nabble.com.