Container based mergeSpills() should respect sortOpts.limit

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2026-03-02
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      ContainerBasedSpiller::mergeSpills incorrectly assumed full consumption of selected spill rows during merge. Under SortOptions::limit, merge can terminate early after producing top-K output, so emitted row count may be less than total rows represented by the selected iterators. This will cause invariant failures in container-backed sorter paths if sort options specifies a limit > 0 with certain numbers of keys.

            Assignee:
            Malik Endsley
            Reporter:
            Malik Endsley
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: