Explain should support custom default read concern

XMLWordPrintableJSON

    • Query Optimization
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently, explain doesn't allow a custom default read concern to be applied. This is confusing because users might see plans that are different from the ones actually being executed. For example, shard filtering is not required for the "available" read concern.

              Assignee:
              Unassigned
              Reporter:
              Henri Nikku
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated: