You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Taras Ledkov (Jira)" <ji...@apache.org> on 2021/10/06 14:31:00 UTC
[jira] [Updated] (IGNITE-12991) Calcite integration. Query registry
& cancellation refactoring
[ https://issues.apache.org/jira/browse/IGNITE-12991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Taras Ledkov updated IGNITE-12991:
----------------------------------
Summary: Calcite integration. Query registry & cancellation refactoring (was: Calcite integration. Query Cancellation)
> Calcite integration. Query registry & cancellation refactoring
> --------------------------------------------------------------
>
> Key: IGNITE-12991
> URL: https://issues.apache.org/jira/browse/IGNITE-12991
> Project: Ignite
> Issue Type: Improvement
> Reporter: Igor Seliverstov
> Assignee: Taras Ledkov
> Priority: Minor
> Labels: calcite2-required, calcite3-required, sql
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Users should have the ability to cancel a query on planning or execution stages.
> Firstly we should have API to retrieve the identifier of the query and API to cancel a query by the identifier.
> For cancel planning see {{AbstractRelOptPlanner.java:91}}, here {{CancelFlag}} is used to cancel planning loop. We need to pass it into a newly created context and bind its state with {{PlanningContext#queryCancel}} to break possible infinite planning loop. See also {{PlanningContext#unwrap}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)