Maybe we should eventually move the `parquet_pruning` option out of `SessionContext` and into the `ParquetReadOptions` structure. As a follow on PR
Open
- Dominant language
- Rust
- Stars
- 9.3k
- Forks
- 2.4k
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 344
Description
Maybe we should eventually move the `parquet_pruning` option out of `SessionContext` and into the `ParquetReadOptions` structure. As a follow on PR
_Originally posted by @alamb in https://github.com/apache/arrow-datafusion/pull/2099#discussion_r841063796_
Contributor guide
Research direction
Start by locating SessionContext, ParquetReadOptions, and the current parquet_pruning handling in the DataFusion source. Trace how the option is read and passed during Parquet scans. Done means parquet_pruning is owned by ParquetReadOptions rather than SessionContext, with affected behavior and tests updated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100