-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
Currently there are many URI options, some of which have corresponding command line (CL) options. When a new URI option is added, it's not clear whether it deserves a corresponding CL option.
We should revisit existing URI options and decide whether to include a CL option for it too. For example, we (perhaps arbitrarily) have CL options that correspond to socketTimeoutMS and serverSelectionTimeoutMS, but not for waitQueueTimeoutMS.
As a possible extra step, we may be able to shrink down the normalization logic between URI and CL options. Whenever we add a URI-CL pair, we also add ~10 lines of code to sync the ConnString and the ToolsOptions structs for that pair. This may be doable in a more concise way by marshalling/unmarshalling the structs and comparing fields using more modular logic – see TOOLS-2585 for the work relevant to this
- split to
-
TOOLS-2585 Simplify normalization logic for URI options and command line options
- Accepted