[
https://issues.apache.org/jira/browse/CAMEL-7378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14371211#comment-14371211
]
Raúl Kripalani commented on CAMEL-7378:
---------------------------------------
Hi [~padewitte],
Please go ahead. As usual, day-to-day work doesn't allow me to keep up with the
work I'd like to do at the Camel community.
A parameter outputType sounds good. By default, if the value is not specified,
backwards-compatibility should be honoured.
We can have 3 values: "DBObjectList", "DBObject" or "DBCursor".
* findOneByQuery would return a DBObject.
* findById would return a DBObject.
* findAll would return a DBObjectList.
It's also important that the operation validates whether the specified
outputType makes sense in its context, e.g. findAll should not allow DBObject;
findById should not allow a DBObjectList (there's no point in creating a list
of 1 element manually...).
Thanks for your help!
Raúl.
> camel-mongodb: Investigate returning DBCursor to enable streaming of large
> result sets
> --------------------------------------------------------------------------------------
>
> Key: CAMEL-7378
> URL: https://issues.apache.org/jira/browse/CAMEL-7378
> Project: Camel
> Issue Type: New Feature
> Components: camel-mongodb
> Affects Versions: 2.13.0
> Reporter: Raúl Kripalani
> Assignee: Raúl Kripalani
>
> See
> http://camel.465427.n5.nabble.com/Does-Camel-MongoDB-use-cursors-on-findAll-td5750352.html
> for context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
