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

Posted to issues@calcite.apache.org by "duan xiong (Jira)" <ji...@apache.org> on 2021/12/02 00:53:00 UTC

[jira] [Commented] (CALCITE-4907) JdbcJoin does not convert Join with always true/false RexNode

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

duan xiong commented on CALCITE-4907:
-------------------------------------

How about this summary "When Join condition is TRUE or FALSE The Calcite can't push down this condition to JdbcJoin"

> JdbcJoin does not convert Join with always true/false RexNode
> -------------------------------------------------------------
>
>                 Key: CALCITE-4907
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4907
>             Project: Calcite
>          Issue Type: Bug
>          Components: jdbc-adapter
>    Affects Versions: 1.28.0
>            Reporter: Francesco Gini
>            Assignee: Francesco Gini
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.29.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Cross joins (LogicalJoin with condition {_}true{_}) are not pushed down in the database when using the JdbcAdapter. This results in implementing the join in memory via _EnumerableNestedLoopJoin_ which is a less efficient implementation.
>  
> JdbcJoin does not handle cases where the condtion is a RexNode that it is always true or false. However, SqlImplementor is coded to handle those conditions (see SqlImplementor.convertConditionToSqlNode).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)