-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Connectivity
-
None
-
2
-
Iteration Seoul
-
Needed
-
We haven’t made a firm decision on this point yet, I think. We added the current behavior, which is to add directConnection=true in these cases, in COMPASS-5012 without actually having discussed it (as far as I know).
Pro:
- It allows connecting to specific secondaries
- It matches what mongosh does (although mongosh does this to match the legacy shell and because it is used for replset administration, neither of which affect Compass)
Con:
- Users are not aware that this happens
- Users may want to connect to the full replica set by default
- It mismatches the driver’s behavior
- is related to
-
COMPASS-5309 Move directConnection=true manipulation from connectMongoClient to convertConnectionModelToInfo
- Closed
- related to
-
COMPASS-5376 Compass ignores directConnection=false
- Closed