You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 1d9b406
Browse filesBrowse the repository at this point in the historyBrowse files
[improvement](be) Admit read-ahead ranges within remaining byte budgets
### What problem does this PR solve?
Issue Number: apache#67611
Related PR: apache#67292
Problem Summary: A wide scan submits the initial windows of all columns together. Whole-batch byte admission rejected every range when their aggregate size exceeded a query or BE budget, discarding useful concurrency even when many ranges could fit. Admit ranges in input order with one linear pass under both budget locks, skip ranges that do not fit, and allocate only admitted buffers. Return null handles at skipped input positions so the existing planner mapping remains intact. Segment coordination registers admitted page slices and completes skipped pages for synchronous fallback. Preserve per-buffer reservation lifetime, allocation rollback, executor failures, and cancellation. Count partially budget-rejected batches without double-counting an executor rejection; configuration defaults, windows, coalescing, and hole filling are unchanged.
### Release note
Retain partial read-ahead concurrency when a planned range batch exceeds its query or BE byte budget.
### Check List (For Author)
- Test: ASAN/PCH BE unit tests through ./run-be-ut.sh --run -j100: 141 tests from 8 suites passed. Coverage includes partial query/BE admission, oversized ranges followed by smaller ranges, original page offsets, consumed-range callbacks, cancellation during allocation, allocation rollback, and executor rejection accounting. Clang-format 16, header hygiene and git diff --check passed.
- Behavior changed: Yes; ranges that fit remain asynchronous while skipped ranges use the original synchronous path.
- Does this need documentation: Yes; update the component behavior in the existing PR and tracking descriptions.
0 commit comments