Skip to content

Example: Communicating Parquet V3 #1

Draft
alamb wants to merge 4 commits into
alamb/update_v2from
alamb/update_v3
Draft

Example: Communicating Parquet V3 #1
alamb wants to merge 4 commits into
alamb/update_v2from
alamb/update_v3

Conversation

@alamb

@alamb alamb commented Jun 5, 2026

Copy link
Copy Markdown
Owner

This draft PR demonstrates what a future Parquet V3 version table could look like, stacked on apache#186.

If we went with a real version 3 it would be represented like this:
Screenshot 2026-06-05 at 9 48 22 AM

Changes:

  • Adds a V3 column to the backwards incompatible feature table.
  • Marks existing V1/V2 features as available in V3.
  • Adds not-yet-released example V3 rows for ALP, FSST, FastLanes integer encoding, and removing path_in_schema.

\

@alamb alamb changed the title Demonstrate Parquet V3 version table Example Parquet V3 version table Jun 5, 2026
@alamb alamb force-pushed the alamb/update_v3 branch from 359a84b to 7b96b11 Compare June 5, 2026 13:36
@alamb alamb force-pushed the alamb/update_v3 branch from 7b96b11 to b26da49 Compare June 5, 2026 13:44
@alamb alamb force-pushed the alamb/update_v2 branch from 522ab74 to 21fb211 Compare June 5, 2026 14:00
@alamb alamb changed the title Example Parquet V3 version table Example: Communicating Parquet V3 Jun 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant