[SERVER-34239] Don't extract readConcernArgs from request when running a DBDirectClient command under a transaction Created: 30/Mar/18 Updated: 29/Oct/23 Resolved: 02/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Maria van Keulen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Storage NYC 2018-04-09 | ||||||||
| Participants: | |||||||||
| Description |
|
When executing a command via DBDirectClient within a transaction, that invocation should not replace the OperationContext readConcernArgs decoration to that of the request. If different than the readConcernArgs setup by the transaction, this will overwrite. |
| Comments |
| Comment by Githook User [ 02/Apr/18 ] |
|
Author: {'email': 'maria@mongodb.com', 'name': 'Maria van Keulen', 'username': 'mvankeulen94'}Message: |