[SERVER-9391] tailable cursors should throw an exception in DBClientCursor when a cursor is not found on the server Created: 18/Apr/13 Updated: 28/Feb/20 Resolved: 28/Feb/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Milkie | Assignee: | Cheahuychou Mao |
| Resolution: | Done | Votes: | 0 |
| Labels: | cxxcopy, neweng, query-44-grooming, servicearch-needsinvestigation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Service Arch 2020-03-09 |
| Participants: |
| Description |
|
dbclientcursor.cpp There does not appear to be a good reason for this, so we should unify the behavior and make all cursor types throw an exception in dataReceived() when the server returns CursorNotFound. |
| Comments |
| Comment by Githook User [ 28/Feb/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com'}Message: |
| Comment by David Storch [ 16/Aug/19 ] |
|
The code that milkie is referring to here appears to still exist in the code base: This internal client code (DBClientCursor) is not maintained by the query team. My best guess is that it should be triaged by Service Architecture, so I'm flagging it as such. |