Make $densify behave the same in replicaset and sharded cluster when db does not exists

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • ALL
    • QE 2024-03-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      On replicaset if we send an aggregation with a $densify stage with a namespace for which the database haven't been created yet and the $densify stage would produce more docs  than the configured internalQueryMaxAllowedDensifyDocs parameter the aggregation will fail with 5897900 error code.

      On the other hand, if the same aggregation is executed on a sharded cluster the aggregation will simply work with no error.

              Assignee:
              Unassigned
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: