bojana-db opened a new pull request, #56703:
URL: https://github.com/apache/spark/pull/56703

   <!--
   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 the SQL function `variant_insert(v, path, val)`, which inserts a value 
into a Variant value at a single JSONPath location.
   
   Details:
   - Object path (e.g. `$.b`): adds a new field; errors with 
`VARIANT_DUPLICATE_KEY`
     if the key already exists;
   - Array path (e.g. `$[N]`): inserts at index `N`, shifting later elements 
right; an
     index past the end pads the gap with variant nulls;
   - Missing intermediate keys/indices along the path are created;
   - Any NULL argument returns NULL;
   - The value may be any expression castable to variant;
   - A new error condition `VARIANT_PATH_TYPE_MISMATCH` is raised when a path 
segment
     is applied to an incompatible value (e.g. an object key on an array); the 
root
     path `$` is rejected with `INVALID_VARIANT_PATH`, and results exceeding 
the size
     limit raise `VARIANT_SIZE_LIMIT`.
   
   ### Why are the changes needed?
   There is no way to add a field or element to a variant; today the only 
option is to convert it to another datatype (e.g. map), mutate, and convert 
back.
   
   
   ### Does this PR introduce _any_ user-facing change?
   Yes, a new SQL function (and Scala/Python `functions` API) plus a new error 
condition `VARIANT_PATH_TYPE_MISMATCH`.
   
   
   ### 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
   


-- 
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]

Reply via email to