-
Type: Bug
-
Resolution: Fixed
-
Priority: Minor - P4
-
Affects Version/s: 1.5.0, 1.5.1, 1.5.2, 1.5.3, 1.5.4
-
Component/s: Connectivity
-
None
-
2
-
Iteration Narwhal
-
Not Needed
Problem Statement/Rationale
using MongoSH with --retryWrites=false does not pass it and the connection string appearing in the "Connection to" does not show it.{}
Steps to Reproduce
Initiate a connection using --retryWrites=false
mongosh --username <pass> --password <pass> --retryWrites=false
In the "Connection to" section no retryWrites is specified:
Connecting to: mongodb://<credentials>@127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+1.5.0
initiating a connection using string URI and inline retryWrites=false
mongosh "mongodb://<user>:<pass>@127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+1.5.0&retryWrites=false"
In the "Connection to" section no retryWrites is specified:
Connecting to: mongodb://<credentials>@127.0.0.1:27017/?directConnection=true&serverSelectionTimeoutMS=2000&appName=mongosh+1.5.0&retryWrites=false
Expected Results
When the connection parameter --retryWrites=false is specified it's expected to be picked up correctly.
Actual Results
The parameter --retryWrites gets ignored if passed as a connection parameter, but gets picked up properly if inserted inline in the connection string URI