Change nested pipeline constraint error message

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              [DO NOT USE] Backlog - Query Optimization
              Reporter:
              Ted Tuckman
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: