[DOCS-11833] Docs for SERVER-35388: Improve misleading error messages for aggregation stages banned in transactions Created: 26/Jun/18  Updated: 13/Nov/23  Resolved: 07/Aug/18

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.0.1, 4.1.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Unassigned
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 5 years, 33 weeks, 1 day ago
Epic Link: DOCS: 4.2 Server/Tools
Story Points: 0.5

 Description   

----------------------------

Original Description

Description:

No documentation summary in engineering ticket

Engineering Ticket Description:

The error messages vary for the aggregation stages not allowed in transactions, as tested in read_concern_snapshot_aggregation.js. Since the readConcern level is upconverted to "snapshot" for transactions, and some of these stages only work with particular readConcern levels, they may error due to the readConcern, which could cause a user to think that the transaction would succeed if they specify a different readConcern level. It would be more helpful to provide an error message that the stage is banned in transactions.

Examples:

"errmsg" : "Aggregation stage $listLocalSessions requires read concern local but
found { readConcern: { level: \"snapshot\" } }",
 
"errmsg" : "$out can not be used with either a 'majority' or 'snapshot' read
concern level",

----------------------------

Description

Scope of changes (files that need work and how much)

Impact to other docs outside of this product

MVP (work and date?)

Resources (e.g. Scope Docs, Invision)


Generated at Thu Feb 08 08:03:45 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.