ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vladimir Ozerov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-11210) SQL: Introduce common logical execution plan for all query types
Date Fri, 01 Mar 2019 09:59:00 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-11210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16781529#comment-16781529

Vladimir Ozerov commented on IGNITE-11210:

Scala re-run: https://ci.ignite.apache.org/viewQueued.html?itemId=3209769

> SQL: Introduce common logical execution plan for all query types
> ----------------------------------------------------------------
>                 Key: IGNITE-11210
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11210
>             Project: Ignite
>          Issue Type: Task
>          Components: sql
>            Reporter: Vladimir Ozerov
>            Assignee: Vladimir Ozerov
>            Priority: Major
>             Fix For: 2.8
>          Time Spent: 10m
>  Remaining Estimate: 0h
> At the moment we have a lot of various cached stuff used for different SQL types (prepared
statements for local queries, two-step queries for distributed queries, update plan for DML).

> What we need instead of having multiple caches is to create common execution plan for
every query, which will hold both DML and SELECT stuff. Approximate content of such a plan:
> # Two-step plan
> # DML plan 
> # Partition pruning stuff
> # May be even cached physical node distribution (for reduce queries) for the given {{AffinityTopologyVersion}}
> # Probably {{AffinityTopologyVersion}}
> Then we will perform a single plan lookup/build per every query execution. In future
we will probably display these plans in SQL views.

This message was sent by Atlassian JIRA

View raw message