[DRIVERS-2664] Remove cursorType option from runCursorCommand API Created: 26/Jun/23 Updated: 25/Jul/23 Resolved: 11/Jul/23 |
|
| Status: | Closed |
| Project: | Drivers |
| Component/s: | CRUD |
| Fix Version/s: | None |
| Type: | Spec Change | Priority: | Unknown |
| Reporter: | Noah Stapp | Assignee: | Shane Harvey |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Epic Link: | DRIVERS-2533 | ||||
| Driver Changes: | Needed | ||||
| Quarter: | FY24Q1 | ||||
| Description |
|
The current spec for runCursorCommand requires a cursorType option that allows users to define the behavior of their cursor with respect to tailable and awaitData. However, users can already set this behavior in the command to be run itself, making this option redundant. It is trivial to implement this option as currently specified, but in the interest of maintaining a minimal, clean interface this option should be removed from the spec. |
| Comments |
| Comment by Shane Harvey [ 11/Jul/23 ] |
|
Spoke the Neal in person. The conclusion we reached is that cursorType is actually needed for drivers that implement the timeoutMode feature in CSOT. |
| Comment by Jeremy Mikola [ 27/Jun/23 ] |
|
I asked about this in the original PR for DRIVERS-2533. Quoting mongodb/specifications#1412:
|