cashmand opened a new pull request, #49234:
URL: https://github.com/apache/spark/pull/49234
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://spark.apache.org/contributing.html
2. Ensure you have added or run the appropriate tests for your PR:
https://spark.apache.org/developer-tools.html
3. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP][SPARK-XXXX] Your PR title ...'.
4. Be sure to keep the PR description updated to reflect all changes.
5. Please write your PR title to summarize what this PR proposes.
6. If possible, provide a concise example to reproduce the issue for a
faster review.
7. If you want to add a new configuration, please read the guideline first
for naming configurations in
'core/src/main/scala/org/apache/spark/internal/config/ConfigEntry.scala'.
8. If you want to add or modify an error type or message, please read the
guideline first in
'common/utils/src/main/resources/error/README.md'.
-->
### What changes were proposed in this pull request?
Adds support for shredding in the Parquet writer code. Currently, the only
way to enable shredding is through a SQLConf that provides the schema to use
for shredding. This doesn't make sense as a user API, and is added only for
testing. The exact API for Spark to determine a shredding schema is still TBD,
but likely candidates are to infer it at the task level by inspecting the first
few rows of data, or add an API to specify the schema for a given column.
Either way, the code in this PR would basically be unchanged, it would just use
a different mechanism to provide the schema.
### Why are the changes needed?
Needed for Variant shredding support.
### Does this PR introduce _any_ user-facing change?
No, the feature is new in Spark 4.0, and is currently disabled, and only
usable as a test feature.
### How was this patch tested?
Added a unit test suite.
### Was this patch authored or co-authored using generative AI tooling?
No.
--
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]
