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
In TableProperties, the properties PARQUET_ROW_GROUP_CHECK_MAX_RECORD_COUNT (write.parquet.row-group-check-max-record-count) and PARQUET_ROW_GROUP_CHECK_MIN_RECORD_COUNT (write.parquet.row-group-check-min-record-count) are actually passed to Parquet as withMaxRowCountForPageSizeCheck and withMinRowCountForPageSizeCheck, respectively. It would be more accurate to rename them as PARQUET_PAGE_SIZE_CHECK_MAX_RECORD_COUNT (write.parquet.page-size-check-max-record-count) and PARQUET_PAGE_SIZE_CHECK_MIN_RECORD_COUNT (write.parquet.page-size-check-min-record-count).
Willingness to contribute
I can contribute a fix for this bug independently
I would be willing to contribute a fix for this bug with guidance from the Iceberg community
I cannot contribute a fix for this bug at this time
The text was updated successfully, but these errors were encountered:
Apache Iceberg version
1.7.1 (latest release)
Query engine
None
Please describe the bug 🐞
In TableProperties, the properties PARQUET_ROW_GROUP_CHECK_MAX_RECORD_COUNT (write.parquet.row-group-check-max-record-count) and PARQUET_ROW_GROUP_CHECK_MIN_RECORD_COUNT (write.parquet.row-group-check-min-record-count) are actually passed to Parquet as withMaxRowCountForPageSizeCheck and withMinRowCountForPageSizeCheck, respectively. It would be more accurate to rename them as PARQUET_PAGE_SIZE_CHECK_MAX_RECORD_COUNT (write.parquet.page-size-check-max-record-count) and PARQUET_PAGE_SIZE_CHECK_MIN_RECORD_COUNT (write.parquet.page-size-check-min-record-count).
Willingness to contribute
The text was updated successfully, but these errors were encountered: