Do not use resolvedViewAggExState after _runAggregate call

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Integration
    • Fully Compatible
    • ALL
    • 200
    • None
    • 3
    • TBD
    • None
    • None
    • None
    • None
    • None
    • None

      This is to resolve BF-37634. The "better" fix is to schedule SERVER-93536 which will make ownership semantics of the AggregationExecutionState more clear, but in the meantime, we should make sure not to use esolvedViewAggExState after _runAggregate call since the object may be unusable at that point.

            Assignee:
            Will Buerger
            Reporter:
            Will Buerger
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: