[
https://issues.apache.org/jira/browse/CALCITE-6242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18079923#comment-18079923
]
Mihai Budiu commented on CALCITE-6242:
--------------------------------------
If it's not just about parsing, the issue has to be broadened.
Can you also check the related issues, e.g., the one which introduced lambdas?
Beware that some implementations may not want to support closures, so maybe you
have to allow for a configuration option in the validator to reject them.
> Enhance lambda closure parsing
> ------------------------------
>
> Key: CALCITE-6242
> URL: https://issues.apache.org/jira/browse/CALCITE-6242
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Hanumath Rao Maduri
> Assignee: terran2010
> Priority: Major
> Labels: pull-request-available
>
> The following query is throwing a "param not found" in calcite whereas the
> same query works fine in apache spark.
> {code:java}
> select *
> from (select array(1, 2, 3) as arr) as t1 inner join
> (select 1 as v) as t2 on "EXISTS"(arr, x -> x = t2.v); {code}
> The following error reported for the above query
> {code:java}
> > java.sql.SQLException: Error while executing SQL "select *
> > from (select array(1, 2, 3) as arr) as t1 inner join
> > (select 1 as v) as t2 on "EXISTS"(arr, x -> x = t2.v)": From line 3,
> > column 54 to line 3, column 57: Param 'T2.V' not found in lambda expression
> > '`X` -> `X` = `T2`.`V`' {code}
> Steps to repro:
> 1. Place the query in lambda.iq
> 2. Run CoreQuidemTest.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
