[
https://issues.apache.org/jira/browse/CALCITE-4907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Gini updated CALCITE-4907:
------------------------------------
Description:
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).
was:
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).
Specifically a cross join is internally represented as a LogicalJoin with
condition true which is not pushed down into the db.
> 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
>
>
> 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)
