-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: None
-
Labels:None
Documentation Request Summary:
No documentation summary in engineering ticket
Engineering Ticket Description:
We may want to support one-shot autocommit batch writes at some point in the future, but we won't for 4.0. To ensure we're leaving the door open for that in the future, any write command that explicitly receives autocommit:true should error.
Additionally, any write command run with readConcern:snapshot outside of a multi-doc transaction should also error.
Finally any write command run inside of a multi-doc transaction should error if a writeConcern is explicitly specified for the write
Scope of changes:
- snapshot read concern
- Already doc'ed snapshot is for transactions only [ See snapshot page| https://docs.mongodb.com/master/reference/read-concern-snapshot]
- autocommit: false
- on commitTxn /abortTxn commands – only listed value is autocommit: false as well as tell people to use drivers/shell helpers
- Inidividual commands – We don't doc how to run the command by passing in lsid/txnNum/stmtId since people should be using drivers/helpers. We only note it: https://docs.mongodb.com/manual/reference/server-sessions/index.html – so no op for us
- write concern within transaction
Impact to other docs outside of this product:
MVP:
Resources:
- documents
-
SERVER-33412 Error on writes with unsupported transaction options
- Closed
- is related to
-
DOCS-11505 Document Transactions
- Closed
- related to
-
DOCS-11599 Docs for SERVER-33295: Kill long-running snapshot transactions
- Closed