Loading...

XML

Word

Printable

JSON

Assigned Teams:

Query Execution
Operating System:
ALL
Steps To Reproduce:

Hide

I came across a bug where running an aggregation explain on a non-existent collection in mongos returns an empty result set, instead of throwing a NamespaceNotFound exception. This is due to the condition in missing cri branch of ClusterAggregate::runAggregate.

One possible fix is to also add a check that the aggregation is not an explain ClusterAggregate::runAggregate on missing cri and to the tassert in AggregationTargeter::make..

I have attached a reproduction script below

Show
I came across a bug where running an aggregation explain on a non-existent collection in mongos returns an empty result set, instead of throwing a NamespaceNotFound exception. This is due to the condition in missing cri branch of ClusterAggregate::runAggregate . One possible fix is to also add a check that the aggregation is not an explain ClusterAggregate::runAggregate on missing cri and to the tassert in AggregationTargeter::make. . I have attached a reproduction script below
Confidence Status:
None
Work Order:
0

is depended on by

COMPASS-8944 Investigate changes in SERVER-100658: Explain on non-existent collection returns empty results for sharded cluster aggregations

is related to

SERVER-18047 Explain on non-existent database should return error

related to

SERVER-100461 Extend the Query Shape Stability suite to assert on all discoverable nodes