[v8.3] [CBR] Incorrect limit propagation results in incorrect CE

XMLWordPrintableJSON

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

      As part of SERVER-122255, we found that the cardinality estimator is failing to check the status result of the limitNodeCard invocation here. The next line checks ceRes != zeroCE, which returns true is ceRes is an error. This results in a bad call to propagateLimit, where we can implicitly create a default QSNEstimate.

      This bug is fixed on master as part of SERVER-122255. This ticket tracks a selective backport of that work to target the limit propagation fix.

        1. diff.txt
          0.7 kB

            Assignee:
            Peter Volk
            Reporter:
            Ben Shteinfeld
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: