Automatically compare explain outputs to detect query optimizer changes

XMLWordPrintableJSON

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

      [Re-purposing this ticket for query plan change detection. For minimizing generated tests see DEVPROD-7361.]

      Looking into the agggregation_multiversion_fuzzer BF-28748 and looking into a particular BFG-1943079, the log file contains the query causing result mismatch, the explain output for v7.0 vs. v7.1, and the unmatched docs v7.0 vs. v7.1.

      What I am looking for, and what can be automated for multiversion fuzzer tests, is to see if there are substantial changes in the query plan to judge if this is a query optimization or query execution issue. In other words, automatically compare explain outputs for v7.0 and v7.1 dismissing known format changes and focusing on query plan changes and report/log the findings.

      This ticket is remotely related to DEVPROD-2810 (show diff between two JSON objects).

            Assignee:
            Unassigned
            Reporter:
            Romans Kasperovics
            Votes:
            2 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: