[SPARK-57804][SQL] Add variant_set expression#57125
Open
bojana-db wants to merge 3 commits into
Open
Conversation
variant_set expressionvariant_set expression
variant_set expressionvariant_set expression
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Adds the SQL function
variant_set(v, path, val[, create_if_missing]), which sets (inserts or replaces) a value in a Variant value at a single JSONPath location.Details:
$.a): replaces the field if it exists; creates it whencreate_if_missingis true (the default);$[N]): replaces the element at indexN; whenNis at or past the end andcreate_if_missingis true, the array is padded with variant nulls up toN;create_if_missingis false, a missing leaf, a missing intermediate, or an out-of-range array index leavesvunchanged;VARIANT_PATH_TYPE_MISMATCHis raised when a path segment is applied to a value of an incompatible type; the root path$is rejected withINVALID_VARIANT_PATH, and results exceeding the size limit raiseVARIANT_SIZE_LIMIT.Why are the changes needed?
Without
variant_set, updating a variant means converting it to another datatype (e.g. map), mutating, and converting back.Does this PR introduce any user-facing change?
Yes, a new SQL function (and Scala/Python
functionsAPI).How was this patch tested?
Unit tests.
Was this patch authored or co-authored using generative AI tooling?
Generated-by: Claude Code with Claude Opus 4.8