liukun4515 commented on PR #1977:
URL: https://github.com/apache/arrow-rs/pull/1977#issuecomment-1171837177
I'm confused about the design of the new API described above
```
fn get_record_reader_by_columns_and_row_ranges(
&mut self,
mask: ProjectionMask,
row_ranges: &RowRanges,
batch_size: usize,
) -> Result<ParquetRecordBatchReader> {
```
I think column index reader should be a function for parquet reader or
parquet-rs, any one who call the parquet reader should get the benefit from
this optimization with a filter.
From your implementation, I find user need to call the lower api and use the
column index to calculate the `ranges`. If so, Any user who want to use the
column index of the parquet should add complex custom logic to fit this lower
interface.
What is your option?
@sunchao @tustvold @viirya
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
