cashmand opened a new pull request, #50025:
URL: https://github.com/apache/spark/pull/50025
<!--
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?
Four new types were added to the Parquet Variant spec
(https://github.com/apache/parquet-format/commit/25f05e73d8cd7f5c83532ce51cb4f4de8ba5f2a2):
UUID, Time, Timestamp(NANOS) and TimestampNTZ(NANOS). They don't correspond to
an existing Spark type, so there is no need to allow them to be constructed in
Spark. But when reading from another tool, we should be able to handle them
gracefully: specifically, casts to JSON/string should work, and SchemaOfVariant
should produce a reasonable result.
This PR only adds support for UUID. Support for the other types should be
similar, mainly differing in the details of casting to string.
### Why are the changes needed?
Support reading Variant values produced by other tools.
### Does this PR introduce _any_ user-facing change?
In Spark 4.0, we would fail when trying to read a Variant value containing
UUID. With this change, we should be able to handle it.
### How was this patch tested?
Added unit tests.
### 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: reviews-unsubscr...@spark.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
