You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2021/08/17 12:28:00 UTC

[jira] [Updated] (IGNITE-15323) Calcite engine. Query lifecycle refactoting

     [ https://issues.apache.org/jira/browse/IGNITE-15323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin updated IGNITE-15323:
-----------------------------------------
    Labels: calcite2-required calcite3-required  (was: )

> Calcite engine. Query lifecycle refactoting
> -------------------------------------------
>
>                 Key: IGNITE-15323
>                 URL: https://issues.apache.org/jira/browse/IGNITE-15323
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Taras Ledkov
>            Assignee: Taras Ledkov
>            Priority: Major
>              Labels: calcite2-required, calcite3-required
>
> Motivation and goals:
> - introduce a {{Query}} abstraction to track a query on all phases: planning, mapping, execution;
> - use one place to query management
> - try to make query phases more isolated, e.g.. now {{PlanningContext}} contains AffinityTopologyVersion and node IDs. It looks like this information has nothing to do with the query planning.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)