-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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.
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
feat: Deprecate top-level write concern option keys #2624
Merged
HanaPearlman
merged 7 commits into
mongodb:3.6
from
HanaPearlman:NODE-1722/3.6/deprecate-wc-options
Nov 30, 2020
Merged
Changes from 1 commit
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
59ce415
deprecate top level write concern fields
HanaPearlman 0d66374
clean
HanaPearlman d4daaee
emphasize deprecation
HanaPearlman 59a4140
gridfs
HanaPearlman 75caa8d
clean
HanaPearlman c8e946d
use bold deprecation docs and include journal in WC
HanaPearlman 6cdceae
wrap config writeConcernMax in writeConcern
HanaPearlman File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev
Previous commit
wrap config writeConcernMax in writeConcern
- Loading branch information
commit 6cdceaeb0a0b25d2c66ac1766e8105cdd016e1d1
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -108,6 +108,12 @@ class NativeConfiguration { | |
Object.assign(dbOptions, { replicaSet: this.options.replicaSet, auto_reconnect: false }); | ||
} | ||
|
||
// Flatten any options nested under `writeConcern` before we make the connection string | ||
if (dbOptions.writeConcern) { | ||
Object.assign(dbOptions, dbOptions.writeConcern); | ||
delete dbOptions.writeConcern; | ||
} | ||
|
||
const urlOptions = { | ||
protocol: 'mongodb', | ||
slashes: true, | ||
|
@@ -224,10 +230,10 @@ class NativeConfiguration { | |
|
||
writeConcernMax() { | ||
if (this.topologyType !== TopologyType.Single) { | ||
return { w: 'majority', wtimeout: 30000 }; | ||
return { writeConcern: { w: 'majority', wtimeout: 30000 } }; | ||
} | ||
|
||
return { w: 1 }; | ||
return { writeConcern: { w: 1 } }; | ||
} | ||
|
||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Per @nbbeeken 's suggestion. The benefit of making this change should be about half as many warnings during testing. |
||
// Accessors and methods Client-Side Encryption | ||
|
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
writeConcernMax
was changed to return awriteConcern
formatted the new way--writeConcern: {w:1, ...}
. Bulk execute takes an actualWriteConcern
object as its first parameter (this was changed in master), so we have to un-wrap thewriteConcernMax
result here.