[CDRIVER-834] Deprecate mongoc_client_kill_cursor Created: 11/Sep/15  Updated: 19/Oct/16  Resolved: 01/Oct/15

Status: Closed
Project: C Driver
Component/s: docs, libmongoc
Affects Version/s: None
Fix Version/s: 1.2-rc0

Type: Improvement Priority: Minor - P4
Reporter: A. Jesse Jiryu Davis Assignee: A. Jesse Jiryu Davis
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by CDRIVER-835 Remove mongoc_client_kill_cursor Backlog
Related
is related to DRIVERS-211 New commands for find, getMore, and k... Closed

 Description   

mongoc_client_kill_cursor doesn't accept a "hint" that would tell the client which server in a replica set or set of mongoses to kill the cursor on, so it's only reliable when connected to a single server.

Beginning with MongoDB 3.2 we begin migrating from the OP_KILLCURSORS message to the killCursors command (DRIVERS-211), which requires the cursor's original database and collection name as well as its id. Again, mongoc_client_kill_cursor doesn't accept these parameters.

Deprecate mongoc_client_kill_cursor since it doesn't work with compound server topologies and will eventually stop working with modern wire protocols. We could replace it with an extended API but it's unnecessary: mongoc_cursor_destroy can always kill the cursor correctly. There's no need for a separate kill-cursors function.



 Comments   
Comment by Githook User [ 01/Oct/15 ]

Author:

{u'username': u'ajdavis', u'name': u'A. Jesse Jiryu Davis', u'email': u'jesse@mongodb.com'}

Message: CDRIVER-834 deprecate mongoc_client_kill_cursor
Branch: 1.2.0-dev
https://github.com/mongodb/mongo-c-driver/commit/3287d5c152303024747258a615577517e36570cf

Generated at Wed Feb 07 21:10:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.