felipepessoto opened a new pull request, #12307:
URL: https://github.com/apache/gluten/pull/12307
## What changes are proposed in this pull request?
Adds `VeloxParquetRowGroupSuite` validating how Gluten's native (Velox)
Parquet writer decides Parquet row-group boundaries, and through which config
channel `parquet.block.size` reaches the native writer.
Motivation: Delta's `DeletionVectorsWithPredicatePushdownSuite.beforeAll`
writes a 1M-row table with `hadoopConf().set("parquet.block.size", 2MB)` and
asserts the file has > 1 row group. Under Gluten the file has a single row
group, so `beforeAll` throws and the whole suite aborts (uncovered by the Delta
Spark UT pipeline #12278).
Three native-write cases (~8MB of int64; `checkNativeWrite` asserts the
write offloads to `ColumnarWriteFilesExec`):
1. default 128MB block size -> 1 row group (control; the Delta-failure
scenario).
2. `spark.gluten.sql.columnar.parquet.write.blockSize=1MB` -> multiple row
groups (the native writer honors its own conf and can split).
3. `parquet.block.size=1MB` set on the runtime Hadoop conf (Delta's
mechanism) -> **asserts > 1 row group and currently FAILS**, because that value
does not reach the native writer (single row group). This case is the
reproduction; it should turn green once the Hadoop-conf block size is plumbed
through to the native writer.
**Draft to run CI** and confirm the reproduction. Case 3 is expected RED
until a follow-up fix.
## How was this patch tested?
This IS the test. The CI run on this PR exercises all three cases.
## Was this patch authored or co-authored using generative AI tooling?
Generated-by: GitHub Copilot CLI (claude-opus-4.8)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
