You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Stanilovsky Evgeny (Jira)" <ji...@apache.org> on 2021/06/30 12:11:00 UTC

[jira] [Resolved] (CALCITE-4673) Correlate variables deduplication are not triggers under COLLECTION_TABLE.

     [ https://issues.apache.org/jira/browse/CALCITE-4673?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stanilovsky Evgeny resolved CALCITE-4673.
-----------------------------------------
    Resolution: Fixed

> Correlate variables deduplication are not triggers under COLLECTION_TABLE.
> --------------------------------------------------------------------------
>
>                 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
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  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)