[SERVER-60086] Currently don't check ReadConcern in a transaction for aggregate command Created: 20/Sep/21 Updated: 29/Oct/23 Resolved: 14/Oct/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ted Tuckman | Assignee: | Wenbin Zhu |
| 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: | Repl 2021-10-18 | ||||||||
| Participants: | |||||||||
| Description |
|
If a stage doesn't run for certain read concerns and that stage is run in a transaction, we don't check for whether the readconcern/stage combo is legal. It looks like the check should be here, but is skipped for the aggregate command. |
| Comments |
| Comment by Githook User [ 14/Oct/21 ] |
|
Author: {'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}Message: |
| Comment by Wenbin Zhu [ 11/Oct/21 ] |
|
There seems to be a bigger issue that we don't check readConcern in multi-document transactions for most of the commands, it's tracked in SERVER-46971 (see this comment). For this ticket we are going to focus on aggregate command. |
| Comment by Samyukta Lanka [ 20/Sep/21 ] |
|
We also specifically don't check whether read concern is supported if it's part of a transaction here, even if we are starting the transaction. |