The execution of $shardedDataDistribution under a causally consistent session should be rejected with a more explicit error message

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1
    • 🟥 DDL
    • None
    • None
    • None
    • None
    • None
    • None

      Today, an attempt to run an aggregation pipeline with a $shardedDataDistribution stage under a causally consistent pipeline raises an unnamed server error during its execution, together with a hard-to-interpret message.

      Since the stage is only meant to collect metrics across shards without snapshot read-like guarantee, such a request may be rejected as soon as it gets received - returning more appropriate messaging to the user.

            Assignee:
            Unassigned
            Reporter:
            Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: