mkarbo opened a new pull request, #7535:
URL: https://github.com/apache/arrow-rs/pull/7535
# Which issue does this PR close?
<!--
We generally require a GitHub issue to be filed for all bug fixes and
enhancements and this helps us generate change logs for our releases. You can
link an issue to this PR using the GitHub syntax. For example `Closes #123`
indicates that this PR will close issue #123.
-->
Closes #7423
# Rationale for this change
<!--
Why are you proposing this change? If this is already explained clearly in
the issue then this section is not needed.
Explaining clearly why changes are proposed helps reviewers understand your
changes and offer better suggestions for fixes.
-->
We need to agree on an API for reading Variant metadata. Based on the work
and discussions in #7452, in this PR we propose an API plus an implementation
(WIP while draft) for reading variant metadata in the parquet-variant crate.
A lot of the work is based on the work in #7452 by @PinkCrow007 and feedback
from @alamb, @scovich, and @Weijun-H.
# What changes are included in this PR?
- Adds Variant enum (and associated structs)
- Adds an API for parsing and reading metadata
- Adds an API for parsing and reading Variant values of various types
We attempt to be result- and validation driven while ensuring
zero-allocations, and we do so avoiding `serde_json`.
We tried to keep the Variant API similar to the `Json::Value` api.
<!--
There is no need to duplicate the description in the issue here but it is
sometimes worth providing a summary of the individual changes in this PR.
-->
# Are there any user-facing changes?
The new API's added in parquet-variant will be user facing.
<!--
If there are user-facing changes then we may require documentation to be
updated before approving the PR.
-->
<!---
If there are any breaking changes to public APIs, please call them out.
-->
There is not, as all this is novel code.
--
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]
