[SERVER-39274] Mongos should not upconvert transaction read concern level to snapshot if none is provided Created: 29/Jan/19 Updated: 29/Oct/23 Resolved: 08/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.8 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | ShardedTxn:RouterSupport | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding 2019-02-11 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
If a user starts a transaction without specifying a read concern level, mongos currently upconverts the level to "snapshot." Instead, mongos should allow an empty read concern level. |
| Comments |
| Comment by Githook User [ 08/Feb/19 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com', 'username': 'jsmulrow'}Message: |