[
https://issues.apache.org/jira/browse/IGNITE-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18749:
---------------------------------------
Description:
We have an issue with long query planning for queries with a few joins. After
benchmarks are introduced in IGNITE-18748 we can choose some sort of parameters
with concrete values ( for example in case we have more than 3 joins and more
than 2 filters) we can implement a simple way to decrease planning time by
disabling some rules for the conditions, for example, join permutation could be
disabled.
Let's implement such optimization to disable some rules for given conditions.
Also, let's add a hint to disable such optimizations which could be useful at
least for our benchmarks.
was:
We have an issue with long query planning for queries with a few joins. After
benchmarks are introduced in IGNITE-18748 we can choose some sort of parameters
with concrete values ( for example in case we have more than 3 joins and more
than 2 filters) we can implement a simple way to decrease planning time by
disabling some rules for the conditions, for example, join permutation could be
disabled.
Let's implement such optimization disable some rules for given conditions.
> Sql. Planner optimization for JOIN (Part 1, simple way)
> -------------------------------------------------------
>
> Key: IGNITE-18749
> URL: https://issues.apache.org/jira/browse/IGNITE-18749
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Yury Gerzhedovich
> Priority: Major
>
> We have an issue with long query planning for queries with a few joins. After
> benchmarks are introduced in IGNITE-18748 we can choose some sort of
> parameters with concrete values ( for example in case we have more than 3
> joins and more than 2 filters) we can implement a simple way to decrease
> planning time by disabling some rules for the conditions, for example, join
> permutation could be disabled.
> Let's implement such optimization to disable some rules for given conditions.
> Also, let's add a hint to disable such optimizations which could be useful at
> least for our benchmarks.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
