You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Andrey Mashenkov (Jira)" <ji...@apache.org> on 2026/03/13 10:55:00 UTC
[jira] [Updated] (IGNITE-28213) SQL. Enable pushing transitive predicates for joins.
[ https://issues.apache.org/jira/browse/IGNITE-28213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrey Mashenkov updated IGNITE-28213:
--------------------------------------
Labels: calcite calcite2-required ignite-3 (was: calcite2-required ignite-3)
> SQL. Enable pushing transitive predicates for joins.
> ----------------------------------------------------
>
> Key: IGNITE-28213
> URL: https://issues.apache.org/jira/browse/IGNITE-28213
> Project: Ignite
> Issue Type: Improvement
> Components: sql ai3
> Reporter: Andrey Mashenkov
> Assignee: Andrey Mashenkov
> Priority: Major
> Labels: calcite, calcite2-required, ignite-3
> Fix For: 3.2
>
>
> The next 2 joins, which have different notation, but semantically are the same.
> {code:java}
> t1 JOIN t2 ON t1.id = t2.id AND t1.id = 1 <-- can pushdown condition with constant into t1 input only
> t1 JOIN t2 ON t1.id = t2.id AND t1.id = 1 AND t2.id = 1 <-- can pushdown conditions with constants into both inputs{code}
> Enabling JOIN_PUSH_TRANSITIVE_PREDICATES rule allows planner to push down predicate to both inputs in the first case.
> Let's enable the rule.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)