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
Parquet decoding is not consistently isolated from I/O work when using separate CPU and I/O runtimes:
Data-file footer and page-index decoding run on the I/O runtime.
Data-file page decoding runs on whichever runtime polls the scan stream, which may be the I/O runtime.
Delete-file footer parsing, page decoding, and delete-filter construction run on the I/O runtime.
This allows CPU-intensive decoding and decompression to compete with storage requests on I/O workers.
Expected behavior: perform Parquet decoding and batch processing on the configured CPU runtime, while keeping storage opens and byte reads on the I/O runtime. Preserve concurrency limits, backpressure, cancellation, and error propagation.
Activity