summaryrefslogtreecommitdiff
path: root/src/mongo/db/write_concern.h
diff options
context:
space:
mode:
authorKaloian Manassiev <kaloian.manassiev@mongodb.com>2015-10-02 17:53:00 -0400
committerKaloian Manassiev <kaloian.manassiev@mongodb.com>2015-10-07 18:33:12 -0400
commit9ba3877df2a0734fbf2148c7c16ca18bdf7d4bfb (patch)
treebf88aa2e6171dbc183922f9fd874a80098077cea /src/mongo/db/write_concern.h
parent8c7455b8260da4ae9ced9285e18c7df8850bf36e (diff)
downloadmongo-9ba3877df2a0734fbf2148c7c16ca18bdf7d4bfb.tar.gz
SERVER-19934 waitForWriteConcern should take write concern parameter
That way sub-operations, which need to wait on a specific write concern, which might be different than the one of the entire operation don't need to change the OperationContext.
Diffstat (limited to 'src/mongo/db/write_concern.h')
-rw-r--r--src/mongo/db/write_concern.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/mongo/db/write_concern.h b/src/mongo/db/write_concern.h
index 31e2bc6c588..72bdfb4d986 100644
--- a/src/mongo/db/write_concern.h
+++ b/src/mongo/db/write_concern.h
@@ -100,6 +100,7 @@ struct WriteConcernResult {
*/
Status waitForWriteConcern(OperationContext* txn,
const repl::OpTime& replOpTime,
+ const WriteConcernOptions& writeConcern,
WriteConcernResult* result);