[SERVER-33865] Use ReadConcernArgs OperationContext decoration on mongos Created: 13/Mar/18 Updated: 29/Oct/23 Resolved: 14/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding 2018-03-26 |
| Participants: |
| Description |
|
The command path on mongod places the command's extracted readConcern args on an operation context decoration. This allows the readConcern to be accessed wherever the operation context is passed. For global point in time reads, we'll need a way to check if a command is running with snapshot readConcern on mongos, which we can do by setting this decoration when mongos first parses readConcern in strategy.cpp. |
| Comments |
| Comment by Githook User [ 14/Mar/18 ] |
|
Author: {'email': 'jack.mulrow@mongodb.com', 'name': 'Jack Mulrow', 'username': 'jsmulrow'}Message: |