[SERVER-32880] Add autocommit parameter to transaction API Created: 24/Jan/18 Updated: 30/Oct/23 Resolved: 21/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Gregory McKeon (Inactive) | Assignee: | Pavithra Vetriselvan |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Sprint: | Repl 2018-02-12, Repl 2018-02-26 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Comments |
| Comment by William Schultz (Inactive) [ 21/Feb/18 ] |
|
Author: {'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}Message: Fix lint |
| Comment by Githook User [ 21/Feb/18 ] |
|
Author: {'email': 'pavithra.vetriselvan@mongodb.com', 'name': 'Pavithra Vetriselvan'}Message: |
| Comment by Githook User [ 15/Feb/18 ] |
|
Author: {'email': 'pavithra.vetriselvan@mongodb.com', 'name': 'Pavithra Vetriselvan'}Message: |
| Comment by A. Jesse Jiryu Davis [ 24/Jan/18 ] |
|
Perfect. |
| Comment by Spencer Brody (Inactive) [ 24/Jan/18 ] |
|
That's a good point Jesse. I believe the current design calls for the earlier transaction to be implicitly aborted, but I can change this to say the new transaction errors and the original is left unaffected. |
| Comment by Gregory McKeon (Inactive) [ 24/Jan/18 ] |
|
Pinging spencer since he isn't a watcher - can we make sure this gets back into the drivers implementation design doc? |
| Comment by A. Jesse Jiryu Davis [ 24/Jan/18 ] |
|
Question, related to eventual support for nested transactions. What happens if a client sends a command with an lsid, a new txnNumber, and autocommit: false, followed by another command with the same lsid, a new txnNumber, and autocommit: false? I propose the server returns an error. Within a session, the current non-autocommit transaction must be committed or aborted before a new transaction begins. This paves the way for eventual nested transactions, if we want to implement them: in the future, the server can choose to nest the new transaction instead of returning an error. |