[SERVER-34240] Don't extract readConcernArgs from request when running a DBDirectClient command under a transaction Created: 30/Mar/18 Updated: 06/Dec/22 Resolved: 30/Mar/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James Wahlin | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| 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. |