[SERVER-46277] Change nested pipeline constraint error message Created: 20/Feb/20  Updated: 06/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Ted Tuckman Assignee: Backlog - Query Optimization
Resolution: Unresolved Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-45620 Have $union introspect the sub-pipeli... Closed
Assigned Teams:
Query Optimization
Participants:

 Description   

Before SERVER-45620 we would allow a nested pipeline with an illegal stage. For example, $facet is not allowed in a $facet. However, we would allow $facet inside a $lookup inside a $facet. This is no longer allowed, but the error message is misleading – in the above example we would report "$lookup is not allowed in $facet". We should look into making the correct information available, or making the error message more generic.


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