You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Ruben Q L (Jira)" <ji...@apache.org> on 2020/02/11 10:45:00 UTC

[jira] [Updated] (CALCITE-3783) PruneEmptyRules#JOIN_RIGHT_INSTANCE wrong behavior for JoinRelType.ANTI

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

Ruben Q L updated CALCITE-3783:
-------------------------------
    Summary: PruneEmptyRules#JOIN_RIGHT_INSTANCE wrong behavior for JoinRelType.ANTI  (was: Rule to remove Join on top of empty Values)

> PruneEmptyRules#JOIN_RIGHT_INSTANCE wrong behavior for JoinRelType.ANTI
> -----------------------------------------------------------------------
>
>                 Key: CALCITE-3783
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3783
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Ruben Q L
>            Assignee: Ruben Q L
>            Priority: Minor
>
> There are some scenarios where a Join with a left/right child being an empty values can be removed:
> - [ LEFT | INNER | SEMI | ANTI ]  JOIN(EmptyValues, X) => EmptyValues
> - [ INNER | SEMI ]  JOIN(X, EmptyValues) => EmptyValues
> - ANTI  (equi)JOIN(X, EmptyValues) => X
> The goal is to create new rule(s) (inside a new class named e.g. JoinRemoveRule) to match and cover these scenarios.



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