Skip to content

Parquet: Support read process for PageIndex (ColumnIndex / OffsetIndex)  #1749

Description

@Ted-Jiang

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.

Describe 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.

Activity

  1. changed the title [-]Parquet: Read support for PageIndex (ColumnIndex / OffsetIndex) [/-] [+]Parquet: Support read for PageIndex (ColumnIndex / OffsetIndex) [/+] on May 26, 2022
  2. changed the title [-]Parquet: Support read for PageIndex (ColumnIndex / OffsetIndex) [/-] [+]Parquet: Support read process for PageIndex (ColumnIndex / OffsetIndex) [/+] on May 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions