Failed SBE collection lookup can cause a null pointer dereference

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 7.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Execution
    • Fully Compatible
    • QE 2023-09-18, QE 2023-10-02, QE 2023-10-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      MultipleCollectionAccessor::lookupCollection can return a null pointer when the collection is not found.  When this gets passed into an SBE generateCollScan call, this null pointer gets passed down to generateGenericCollScan and dereferenced (or generateClusteredCollScan and dereferenced), causing a null pointer exception.  This can happen with other 
      getCurrentCollection calls as well; here is an example with generateIndexScan.

            Assignee:
            Mihai Andrei
            Reporter:
            Hugh Tong (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: