[
https://issues.apache.org/jira/browse/IGNITE-24167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-24167:
--------------------------------------
Fix Version/s: 3.1
> Sql. Introduce heuristics to optimize join order
> --------------------------------------------------
>
> Key: IGNITE-24167
> URL: https://issues.apache.org/jira/browse/IGNITE-24167
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Konstantin Orlov
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.1
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment, join-order optimization is part of the cost-based phase. We
> have only JOIN_COMMUTE rule and rules which exchange one of the join input
> with input of a nested join (e.g. (A join B) join C becomes (A join C) join
> B). Such an approach is highly inefficient, thus maximum number of relation
> to optimize join order currently set to 5.
> In the mean time, analytical workload tends to join higher number of tables
> (TPC-H queries 5, 7, 8, and 9; TPC-DS queries 64, 85, and 91).
> Let's introduce heuristic phase to optimize join orders, that will handle
> joins of more than 5 relations.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
