Hi, We use Mongo cursors to read from the DB. But a DBCursor is not something we can return to the route because not all technologies support Streams, Cursors, Chunking, etc. For example, how would you go about returning a DBCursor to a JMS endpoint?
That's why we offer the skipping and limiting option so you can perform pagination in such scenarios. You can also specify a batch size. Take a look at the component page for further details. Hope that helps! Raúl. > On 17 Apr 2014, at 15:41, Ephemeris Lappis <[email protected]> wrote: > > Hello. > > After some tests, it seems that the Camel MongoDB "findAll" operation tries > to load all the matching queried data into memory before process them. With > collections whose content is about tens millions of documents, this > naturally leads to OutOfMemoryErrors... > > Does this component may use cursors to read the input data and stream them ? > > An idea ? > > Thanks in advance. > > Regards. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Does-Camel-MongoDB-use-cursors-on-findAll-tp5750352.html > Sent from the Camel - Users mailing list archive at Nabble.com.
