bojana-db opened a new pull request, #56864:
URL: https://github.com/apache/spark/pull/56864
<!--
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_strip_nulls(v[, includeArrays])`, which
recursively removes Variant null fields from objects (and, by default, Variant
null elements from arrays) in a Variant value.
Details:
- Object path: a field whose value is a Variant null (the JSON null literal)
is removed entirely; recursion walks nested objects and arrays at all levels;
- includeArrays (BOOLEAN, default true): when true, Variant null elements
are also removed from arrays; when false, array null elements are kept, but
null fields of objects nested anywhere (including inside arrays) are still
stripped;
- Empty containers are preserved: an object/array emptied by stripping stays
{} / []; the parent is never collapsed to NULL;
- Non-container inputs — scalars and a top-level Variant null
(parse_json('null')) — are returned unchanged;
- NULL intolerant: any NULL argument returns NULL.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
There is no built-in way to drop Variant null entries from a Variant; today
users must convert it to another type (e.g. a map) and back.
### Does this PR introduce _any_ user-facing change?
Yes, a new SQL function (and Scala/Python `functions` API.
### 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]
