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 b9396d9
Browse filesBrowse the repository at this point in the historyBrowse files
Issue Number: None
Related PR: apache#67292
Problem Summary: Query read-ahead must publish only buffers that were actually consumed, preserve caller-visible IO statistics, and honor the original cache-write policy. Centralize query read-ahead construction so SegmentIterator and exact row-id readers share the same byte windows, range planner, page-cache probe, scheduler, and writeback setup. Each asynchronous submission owns its statistics and File Cache epoch; the first consumed page publishes the completed range once, while no-write and remote-only requests skip cache writeback.
Enable consumed query read-ahead ranges to populate File Cache when asynchronous cache writeback is enabled.
- Test: Unit Test
- ./run-be-ut.sh --run --filter=AsyncCachedRemoteFileReaderTest.*:SegmentReadAheadTest.*:SegmentIteratorReadAheadTest.*:ColumnReaderTest.*ReadAhead* -j100
- Behavior changed: Yes; consumed successful query read-ahead ranges now contribute IO statistics and enter cache writeback when policy permits.
- Does this need documentation: Yes; covered by the read-ahead and hole-fill design document.
0 commit comments