-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Minor - P4
-
None
-
Affects Version/s: None
-
Component/s: None
-
2
-
None
-
None
-
None
-
None
-
None
-
None
-
None
When the MongoDB server returns an IllegalOperation error (code 20), the NODE driver reports a misleading message:
> await db.createCollection('system.buckets.foo');
Uncaught:
MongoServerError: This MongoDB deployment does not support retryable writes. Please add retryWrites=false to your connection string.
Even for errors completely unrelated to retryWrites, end even if already using --retryWrites=false (which does not matter anyway).
Expected Behavior
As a... Node Driver user
I expect... to see actual server message
When... server returns an IllegalOperation error
Actual Behavior and Impact
- What is the actual behavior?
- If bug: What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?
- The actual behavior: hard-coded error text "This MongoDB deployment does not support retryable writes. Please add retryWrites=false to your connection string.", which is not at all correct.
- Bug: Unknown number of impacted customers. This bug has been in the codebase for a while now.
Dependencies
- None
Risks/Unknowns
- Risk: actual error text makes it back to caller.
Acceptance Criteria
Implementation Requirements
- IllegalOperation errors contain relevant error details
Testing Requirements
- Integration tests exist to verify this issue
Documentation Requirements
- None
Follow Up Requirements
- None
- depends on
-
DRIVERS-3648 Add unified tests for code-20 passthrough
-
- Needs Triage
-