[ https://issues.apache.org/jira/browse/ARROW-10620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Lamb resolved ARROW-10620. --------------------------------- Fix Version/s: 3.0.0 Resolution: Fixed Issue resolved by pull request 8682 [https://github.com/apache/arrow/pull/8682] > [Rust][Parquet] move column chunk range logic to metadata.rs > ------------------------------------------------------------ > > Key: ARROW-10620 > URL: https://issues.apache.org/jira/browse/ARROW-10620 > Project: Apache Arrow > Issue Type: Bug > Components: Rust > Reporter: Remi Dettai > Priority: Minor > Labels: pull-request-available > Fix For: 3.0.0 > > Time Spent: 50m > Remaining Estimate: 0h > > Getting the range of bytes of a column chunk inside a parquet file can be > useful for external crates (for instance if they want to pre-fetch the > columns), and is not completely obvious (it is enough to take a look at [1] > and [2] to see that things can quickly get messy). > I think it would be nice to move this logic in the metadata definition rather > than have lost it in the middle of the reader implem. > [1] > https://stackoverflow.com/questions/55225108/why-is-dictionary-page-offset-0-for-plain-dictionary-encoding/ > [2] https://issues.apache.org/jira/browse/PARQUET-816 -- This message was sent by Atlassian Jira (v8.3.4#803005)