Skip to content

[format] Pass through parquet statistics and page-size-check config in RowDataParquetBuilder#7956

Merged
JingsongLi merged 1 commit into
apache:masterfrom
yugan95:parquet-0410
May 25, 2026
Merged

[format] Pass through parquet statistics and page-size-check config in RowDataParquetBuilder#7956
JingsongLi merged 1 commit into
apache:masterfrom
yugan95:parquet-0410

Conversation

@yugan95
Copy link
Copy Markdown
Contributor

@yugan95 yugan95 commented May 25, 2026

Purpose

Pass through parquet statistics and page-size-check configuration in RowDataParquetBuilder.

Currently RowDataParquetBuilder does not forward the following Parquet config keys to the writer:

  • parquet.statistics.truncate.length
  • parquet.columnindex.truncate.length
  • parquet.page.size.row.check.min
  • parquet.page.size.row.check.max

Without these, users cannot tune Parquet page-size checking behavior or control the truncation length of statistics and column indexes. This is especially relevant for tables with large records, where the default page-size check thresholds can lead to oversized pages.

Split out from #7621 per reviewer feedback, as this is an independent enhancement.

Changes

  • RowDataParquetBuilder: add .withMinRowCountForPageSizeCheck(),
    .withMaxRowCountForPageSizeCheck(), .withStatisticsTruncateLength(), .withColumnIndexTruncateLength() to the builder chain, reading from the existing Hadoop Configuration with Parquet's default values as fallback.

Tests

Existing Parquet write tests cover the default config path. The new keys follow the same pattern as other builder options (e.g. withDictionaryPageSize, withPageSize) and use Parquet's built-in defaults when not set.

API and Format

N/A — no public API or format changes. Users can now set these keys via table properties, using the same mechanism as other Parquet config keys.

Documentation

N/A

@JingsongLi
Copy link
Copy Markdown
Contributor

+1

@JingsongLi JingsongLi merged commit 3ff34a3 into apache:master May 25, 2026
12 checks passed
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.

2 participants