feat(sql): support nested lambda functions#19936
Merged
Merged
Conversation
7b4afc5 to
50e2756
Compare
b41sh
approved these changes
May 29, 2026
50e2756 to
80683e8
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 80683e88d7
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
80683e8 to
7e771c6
Compare
Remove the restriction that prevented lambda functions from being used inside other lambda functions. This aligns with Snowflake's TRANSFORM behavior and enables multi-level array transformations without requiring LATERAL FLATTEN workarounds. The evaluator already supports recursive lambda execution via eval_lambda_block creating a new Evaluator. The restriction was only in the type checker as a conservative guard from the initial lambda implementation (PR #12217, 2023).
7e771c6 to
01d6046
Compare
Contributor
Docker Image for PR
|
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.
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
Remove the restriction that prevented lambda functions from being used inside other lambda functions, aligning with Snowflake's
TRANSFORMbehavior.Problem: Multi-level nested array transformations (e.g.
events[*].attributes[*].value.stringValue) required verbose LATERAL FLATTEN + GROUP BY workarounds becausejson_array_transformcould not be nested inside anotherjson_array_transform.Root cause: A conservative guard added in the initial lambda implementation (PR #12217, 2023) blocked all lambda-in-lambda usage at the type checker level. However, the evaluator already supports recursive execution —
eval_lambda_blockcreates a newEvaluatorthat naturally handles nestedLambdaFunctionCallnodes.Fix:
UnqualifiedWildcardInVisible— when a lambda parameter has the same name as an outer column, the outer column is hidden from unqualified lookup but remains accessible via qualified reference (e.g.table.column). This preserves backward compatibility with existing queries.After this change:
Tests
Type of change
This change is