Skip to content

DOCS-13508 add changelog entry for writeconcern error in mongos #4005

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2020
Merged

DOCS-13508 add changelog entry for writeconcern error in mongos #4005

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions source/release-notes/4.4-compatibility.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,6 +138,12 @@ General Changes
MMAPv1 field
``replSetGetStatus.initialSyncStatus.fetchedMissingDocs`` in its
output.

- :binary:`~bin.mongos` now logs an error if you pass an empty
``writeConcern`` value i.e. ``writeConcern: {}`` to a command
that does not support write concerns. In earlier versions,
:binary:`~bin.mongos` ignores an empty ``writeConcern`` value for
these commands.

.. _4.4-compatibility-enabled:

Expand Down