[SERVER-35403] Should not attempt to close a non-existing cursor Created: 05/Jun/18 Updated: 29/Oct/23 Resolved: 05/Jun/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc3, 4.1.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | todo_in_code | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Backport Requested: |
v4.0
|
||||||||||||||||
| Sprint: | TIG 2018-06-18 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 0 | ||||||||||||||||
| Description |
|
Calling close on a cursor will attempt to close the cursor even if the cursor does not exist. Which causes an exception to be thrown. This becomes a problem if we hit an issue trying to create the cursor. The calling code does not know whether the cursor was created or not so cannot know if it can safely call close without viewing the internals of the cursor code. |
| Comments |
| Comment by Githook User [ 05/Jun/18 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit dd5a8dd1e836d4b442cd727d246f2d0bd9d51543) |
| Comment by Githook User [ 05/Jun/18 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: |