[SERVER-60749] Change internal client to stop issuing the "availableQueryOptions" command Created: 15/Oct/21 Updated: 29/Oct/23 Resolved: 25/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| 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: | QE 2021-11-01 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
When DBClientConnection is asked by a caller to run an exhaust query, it has logic to check that the remote node supports exhaust. This is implemented by running the "availableQueryOptions" command against the remote node. We should remove this logic from the internal client for a few reasons:
|
| Comments |
| Comment by Githook User [ 25/Oct/21 ] |
|
Author: {'name': 'David Storch', 'email': 'david.storch@mongodb.com', 'username': 'dstorch'}Message: |
| Comment by David Storch [ 15/Oct/21 ] |
|
Once this ticket is complete, we should file a follow-up ticket under which we will actually remove the implementation of the "availableQueryOptions" command. I don't think this can be done just yet, since a 5.0 node could issue "availableQueryOptions" to a 5.1, 5.2, 5.3, or 6.0 node in a mixed version cluster. |