[SERVER-36091] DBClientConnection::query() should pass all results to callback Created: 12/Jul/18  Updated: 29/Oct/23  Resolved: 06/Aug/18

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: 4.0.0
Fix Version/s: 4.1.2

Type: Bug Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Matthew Russotto
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-36096 Convert CollectionCloner to use DBCli... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Repl 2018-07-30, Repl 2018-08-13
Participants:

 Description   

When the exhaust option is available, DBClientConnection::query() does not pass all of its results to the provided callback function.



 Comments   
Comment by Githook User [ 06/Aug/18 ]

Author:

{'username': 'mtrussotto', 'name': 'Matthew Russotto', 'email': 'matthew.russotto@10gen.com'}

Message: SERVER-36091 DBClientConnection::query() should pass all results to callback

DBClientConnection::query currently relies on exhaust cursor support in DBClientCursor working in
a particular way, which is true for OP_QUERY exhaust but will not be true for OP_CMD exhaust. This
change makes it more general, avoiding exhaust-specfic APIs.
Branch: master
https://github.com/mongodb/mongo/commit/c35307abae44b2291a6b82571a1defff2bf188a3

Comment by Matthew Russotto [ 25/Jul/18 ]

I think this isn't a bug with the OP_QUERY implementation.

Comment by Tess Avitabile (Inactive) [ 12/Jul/18 ]

david.storch, let me know if you would like us to backport this fix. I don't think this particular DBClientConnection::query() function was used very much.

Generated at Thu Feb 08 04:42:00 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.