[ 
https://issues.apache.org/jira/browse/CALCITE-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17385710#comment-17385710
 ] 

Julian Hyde commented on CALCITE-4673:
--------------------------------------

Rephrasing my previous question: what is the minimal test case?

Does this bug reproduce if the query has LATERAL but no table function? Does 
this bug reproduce if a table function is not in a sub-query without LATERAL 
(say a scalar sub-query or EXISTS)?

In the test case in SqlToRelConverterTest, it is not clear what constitutes a 
"good" output (or conversely, how the output looked before the bug was fixed). 
Comments would help.

> Correlate variables deduplication is not triggered when custom table function 
> presented.
> ----------------------------------------------------------------------------------------
>
>                 Key: CALCITE-4673
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4673
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.27.0
>            Reporter: Stanilovsky Evgeny
>            Assignee: Stanilovsky Evgeny
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.28.0
>
>         Attachments: code-sample-UDF-in-quidem.patch
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> request like:
> {noformat}
> select e.deptno, (select * from lateral table(DEDUP(e.deptno, e.deptno))) 
> from emp e;
> {noformat}
> shows 2 different correlates, while it only one.
> {noformat}
> LogicalProject(DEPTNO=[$7], EXPR$1=[$SCALAR_QUERY({
> LogicalProject(NAME=[$0])
>   LogicalTableFunctionScan(invocation=[DEDUP($cor0.DEPTNO, $cor1.DEPTNO)], 
> rowType=[RecordType(VARCHAR(1024) NAME)])
> })])
>   LogicalTableScan(table=[[CATALOG, SALES, EMP]])
> {noformat}
> [dev-list 
> discussion|https://lists.apache.org/thread.html/re20d580a979585ae946d61df80a345c70ae2b5a92577a8b5db1e2c50%40<dev.calcite.apache.org>]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to