[Join Optimization] Create PBT to test correctness of index fingerprint invalidation of join plan cache

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

      We can use the exposed index fingerprint from explain (after SERVER-132693) to implement a PBT that generates random join-eligible queries and changes the set of indexes. One property we could assert on is that if the fingerprints match, then the plans we generate (we can generate multiple using the random reorderer) should never use the newly added/removed/modified index.

            Assignee:
            Unassigned
            Reporter:
            Naafiyan Ahmed
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: