[
https://issues.apache.org/jira/browse/CALCITE-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17392703#comment-17392703
]
Julian Hyde commented on CALCITE-4673:
--------------------------------------
Yeah, I know it's a bit strange to file a bug that can't be reproduced on
master, but it's better than not filing a bug.
Sorry to labor this. But I suspect that this problem exists for every kind of
sub-query. You found it for one kind. I just happened to find it when I added
two new types of sub-query. It's reasonable to assume that it exists for all
the others, too. Can you write test cases for correlated IN and EXISTS, and see
if those have the same problem?
> 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: Evgeny Stanilovsky
> Assignee: Evgeny Stanilovsky
> 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)
