[SERVER-18296] Cleanup DBClientCursor error handling Created: 01/May/15  Updated: 10/May/22

Status: Backlog
Project: Core Server
Component/s: Internal Client, Networking, Querying
Affects Version/s: 3.1.2
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Daniel Alabi Assignee: DO NOT USE - Backlog - Platform Team
Resolution: Unresolved Votes: 0
Labels: move-sa, platforms-re-triaged
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Description   

In DBClientBase::query, if DBClientCursor can't be initialized, we return NULL. We should throw (perhaps, a UserException) instead.
Once this is done, we can get rid of _safeCursor in cluster_client_internal.h.

https://github.com/mongodb/mongo/blob/9bf7c1df8376377197f998f35566cc7e7f5ca03e/src/mongo/client/dbclient.cpp#L1007



 Comments   
Comment by Steven Vannelli [ 10/May/22 ]

Moving this ticket to the Backlog and removing the "Backlog" fixVersion as per our latest policy for using fixVersions.

Comment by Adam Midvidy [ 11/May/15 ]

Marking this as "planned but not scheduled" as it isn't quite worth doing on its own and we will get to this when we (eventually...) do a larger cleanup of the DBClient hierarchy.

Generated at Thu Feb 08 03:47:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.