Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.7.4
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2018-04-23
Linked BF Score:
45
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

is duplicated by

SERVER-33047 Error if write concern provided as part of a write of a multi-statement transaction

Closed

SERVER-33591 Cleanup interaction of write concerns and transactions

Closed

SERVER-33592 Disallow writes with snapshot read concern outside transactions

Closed

related to

SERVER-34051 Require autocommit:false on all operations as part of an ongoing transaction

Closed

Assignee:: Matthew Russotto
Reporter:: Spencer Brody (Inactive)
Participants:: Eric Milkie, Githook User, Matthew Russotto, Spencer Brody, Tess Avitabile
Votes:: 0 Vote for this issue
Watchers:: 6 Start watching this issue

Created:: Feb 20 2018 10:35:13 PM UTC
Updated:: Oct 29 2023 10:34:34 PM UTC
Resolved:: Apr 13 2018 08:18:51 PM UTC

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates