[SERVER-51431] BF Day: Transaction read concerns are not honored by mongo shell Created: 08/Oct/20 Updated: 29/Oct/23 Resolved: 29/Mar/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Raiden Worley (Inactive) |
| 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 | ||||||||||||
| Backport Requested: |
v4.9
|
||||||||||||
| Sprint: | STM 2021-03-22, STM 2021-04-05 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 129 | ||||||||||||
| Story Points: | 2 | ||||||||||||
| Description |
|
The mongo shell doesn't seem to honor the following statement from the documentation: "If the transaction-level read concern is unset, the transaction-level read concern defaults to the session-level read concern." An operation is always executed with the session-level read concern (if set) while the eventual transaction read-level concern - set on the session when starting a new transaction - is completely ignored. It should be adopted a solution similar to the one implemented by nodejs driver that is assigning a read-concern to an operation respecting the correct order (transaction RC || session RC || client RC). |
| Comments |
| Comment by Githook User [ 29/Mar/21 ] |
|
Author: {'name': 'Raiden Worley', 'email': 'carl.worley@mongodb.com'}Message: |