[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:
Related
related to SERVER-60038 Ban setWindowFields in transaction wi... Closed
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: SERVER-60086 Add read concern check for aggregate commands.
Branch: master
https://github.com/mongodb/mongo/commit/16c954fa873af6c06ae5428b8af7db3363ae8747

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.

Generated at Thu Feb 08 05:48:55 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.