[SERVER-22515] Implement Server Selection Spec's changes for runCommand and command helpers Created: 08/Feb/16  Updated: 06/Dec/22  Resolved: 03/Dec/21

Status: Closed
Project: Core Server
Component/s: Shell
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: A. Jesse Jiryu Davis Assignee: Backlog - Server Tooling and Methods (STM) (Inactive)
Resolution: Won't Fix Votes: 0
Labels: move-stm
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-22516 mongos should apply client's read pre... Backlog
Assigned Teams:
Server Tooling & Methods
Participants:

 Description   

If the shell is committed to matching the drivers Server Selection Spec, it needs to be updated to match behavior we decided on for drivers last year. See this section of the Server Selection Spec:

https://github.com/mongodb/specifications/blob/master/source/server-selection/server-selection.rst#use-of-read-preferences-with-commands

"runCommand" MUST use the default readPreference, "primary", regardless of previous calls to setReadPrefs(). "runCommand" SHOULD also accept an argument that allows the user to set an explicit read preference.

Command-specific helpers like "count", "getIndexes", "aggregate", and so on need to be reviewed and updated to match the spec's point number 3 that describes how helper methods behave.

Please ask david.golden, me, or any of the advisors on the spec for questions and justifications.



 Comments   
Comment by Brooke Miller [ 03/Dec/21 ]

STM doesn't have bandwidth to pick this up, so we're closing as won't fix. However, if other teams have capacity and would like to pursue this, please feel free to pick this up.   

Generated at Thu Feb 08 04:00:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.