[SERVER-36170] Ignore (but continue to accept) the 'collection' field of a getMore request Created: 17/Jul/18 Updated: 06/Dec/22 Resolved: 07/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Participants: |
| Description |
|
When all cursors are globally managed, the collection name will not be useful. Only the cursor id will be required, both to locate the server-side ClientCursor and to perform authorization checks. |
| Comments |
| Comment by David Storch [ 07/Feb/19 ] |
|
We've decided not to pursue this change as part of the "all cursors globally managed project". The namespace of the getMore request is still used internally for auth checks. This could be slightly simplified, but making this change is not currently a priority. |
| Comment by David Storch [ 31/Oct/18 ] |
|
ravind.kumar, thanks for the heads up, I've marked this as "Documentation Changes: Needed". SERVER-31695 tracks the general work to allow queries to survive collection rename, although I believe this ticket may be a prerequisite. For that reason, I also marked SERVER-31695 as "Documentation Changes: Needed".
That's right, none of the changes in the "All cursors globally managed" project will impact the behavior of change streams. |
| Comment by Ravind Kumar (Inactive) [ 29/Oct/18 ] |
|
Please mark this as documentation needed, as we can remove the related blurb in the warning admonition for the renameCollection command. To confirm though - this change would not affect invalidation of change streams against a collection, correct? |