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
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
follow #1705
Goal:
Index granularity - per page (used row Group).
Make selective scans on both sorting & non-sorting columns efficient(maybe).
No additional I/O & deserialization costs for non-selective filter.
Describe the solution you'd like
There is already store the PageIndex Index just above the footer. Store offset and length in col metadata.
Using these index with Row Alignment filter page without decode+decompress.
Ted-Jiang
changed the title
Parquet: Read support for PageIndex (ColumnIndex / OffsetIndex)
Parquet: Support read for PageIndex (ColumnIndex / OffsetIndex)
May 26, 2022
Ted-Jiang
changed the title
Parquet: Support read for PageIndex (ColumnIndex / OffsetIndex)
Parquet: Support read process for PageIndex (ColumnIndex / OffsetIndex)
May 26, 2022
Is your feature request related to a problem or challenge? Please describe what you are trying to do.
follow #1705
Goal:
Index granularity - per page (used row Group).
Make selective scans on both sorting & non-sorting columns efficient(maybe).
No additional I/O & deserialization costs for non-selective filter.
Describe the solution you'd like
There is already store the PageIndex Index just above the footer. Store offset and length in col metadata.
Using these index with
Row Alignment
filter page without decode+decompress.PageIndex
from column metadata #1761Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: