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

[jira] [Resolved] (IGNITE-14810) Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.

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

Stanilovsky Evgeny resolved IGNITE-14810.
-----------------------------------------
    Resolution: Not A Bug

> Calcite. Simple JOIN with f1=f2 cannot be planned with CNLJ.
> ------------------------------------------------------------
>
>                 Key: IGNITE-14810
>                 URL: https://issues.apache.org/jira/browse/IGNITE-14810
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Stanilovsky Evgeny
>            Priority: Major
>              Labels: calcite
>
> For now simple JOIN requests like:
> {noformat}
> SELECT * FROM integers FULL OUTER JOIN integers2 ON integers.i=integers2.k ORDER BY i
> {noformat}
> can be planned only through MergeJoin or NestedLoopJoin it would be useful to extend it with CNLJ too. Starting point : {{FilterSpoolMergeToSortedIndexSpoolRule#onMatch}}
> We have to add new rule {{FilterSpoolMergeToSortedIndexSpoolRule_ForceCollation}} which forces collation by the filter condition. 



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