Skip to content

[branch-53] backport: Support Spark array_contains builtin function (#20685)#20914

Merged
alamb merged 1 commit intoapache:branch-53from
comphead:b53
Mar 12, 2026
Merged

[branch-53] backport: Support Spark array_contains builtin function (#20685)#20914
alamb merged 1 commit intoapache:branch-53from
comphead:b53

Conversation

@comphead
Copy link
Contributor

Which issue does this PR close?

Rationale for this change

What changes are included in this PR?

The Spark function is actual wrapper on top of array_has function. After result is being produced the nulls mask is set respectively for the output indices which correspond to input rows having nulls

Are these changes tested?

Are there any user-facing changes?

Which issue does this PR close?

  • Closes #.

Rationale for this change

What changes are included in this PR?

Are these changes tested?

Are there any user-facing changes?

## 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 apache#20611 .

## 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.
-->

## What changes are included in this PR?

The Spark function is actual wrapper on top of `array_has` function.
After result is being produced the nulls mask is set respectively for
the output indices which correspond to input rows having nulls

<!--
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 these changes tested?

<!--
We typically require tests for all PRs in order to:
1. Prevent the code from being accidentally broken by subsequent changes
2. Serve as another way to document the expected behavior of the code

If tests are not included in your PR, please explain why (for example,
are they covered by existing tests)?
-->

## Are there any user-facing changes?

<!--
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 add the `api
change` label.
-->
@github-actions github-actions bot added sqllogictest SQL Logic Tests (.slt) spark labels Mar 12, 2026
@alamb alamb merged commit b7ccb53 into apache:branch-53 Mar 12, 2026
28 checks passed
@alamb
Copy link
Contributor

alamb commented Mar 12, 2026

Let's get 53 ready

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

spark sqllogictest SQL Logic Tests (.slt)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants