You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Yury Gerzhedovich (Jira)" <ji...@apache.org> on 2023/03/03 15:08:00 UTC
[jira] [Commented] (IGNITE-18749) Sql. Planner optimization for JOIN (Part 1, simple way)
[ https://issues.apache.org/jira/browse/IGNITE-18749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17696186#comment-17696186 ]
Yury Gerzhedovich commented on IGNITE-18749:
--------------------------------------------
[~korlov] , LGTM. Thanks for the contribution!
> 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
> Assignee: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
> Fix For: 3.0.0-beta2
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> 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)