[DRIVERS-598] Change stream spec should be more explicit about how to kill the cursor before resuming Created: 11/Jan/19 Updated: 22/Feb/23 Resolved: 22/Feb/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | Change Streams |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Katherine Walker (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Driver Compliance: |
|
||||||||||||||||||||||||||||
| Description |
|
Any exceptions or errors that occur during the process of killing the cursor should be suppressed including both errors returned by the ``killCursor`` command and exceptions thrown by opening, writing to, or reading from the socket. See spec change for details. |
| Comments |
| Comment by Kristofer Brandow (Inactive) [ 04/Feb/19 ] |
|
Go already suppresses errors from killCursors. |
| Comment by Daniel Aprahamian (Inactive) [ 01/Feb/19 ] |
|
Node already suppresses errors when closing a cursor. |
| Comment by Shane Harvey [ 01/Feb/19 ] |
|
Pymongo already suppresses errors from its Cursor.close() method. |