[SERVER-57461] Remove SPLIT_LIMITED_SORT and associated QueryPlanner code Created: 04/Jun/21 Updated: 29/Oct/23 Resolved: 31/Jul/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Eric Cox (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Query Execution 2021-07-26, QE 2021-08-09 | ||||||||
| Participants: | |||||||||
| Description |
|
This code is necessary for queries passed to the server as legacy OP_QUERY find. Since we are removing support for OP_QUERY find, SPLIT_LIMITED_SORT can (eventually) be deleted. We suspect that this code deletion cannot be done until after we release 6.0 in order to ensure that the 5.0/5.1 upgrade/downgrade continues to function as expected. In particular, a 5.0 mongos could receive an OP_QUERY find with ntoreturn, and forward this request to the shards as an OP_MSG find command with ntoreturn. This find command may require SPLIT_LIMITED_SORT to work. If this is correct, then the ticket should be scheduled post-6.0 alongside tasks such as |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 31/Jul/21 ] |
|
Author: {'name': 'Eric Cox', 'email': 'eric.cox@mongodb.com', 'username': 'ericox'}Message: |