You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Evgeny Stanilovsky (Jira)" <ji...@apache.org> on 2023/01/31 07:41:00 UTC

[jira] [Assigned] (IGNITE-17950) Sql. Investigate way of reworking query cancellation flow

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

Evgeny Stanilovsky reassigned IGNITE-17950:
-------------------------------------------

    Assignee: Evgeny Stanilovsky

> Sql. Investigate way of reworking query cancellation flow
> ---------------------------------------------------------
>
>                 Key: IGNITE-17950
>                 URL: https://issues.apache.org/jira/browse/IGNITE-17950
>             Project: Ignite
>          Issue Type: Improvement
>          Components: sql
>            Reporter: Konstantin Orlov
>            Assignee: Evgeny Stanilovsky
>            Priority: Major
>              Labels: ignite-3
>
> To prevent locks from being held indefinitely, we need to make sure that the root fragment of the query is the last to cancel.
> Let's investigate how to achieve  the goal with rework the query cancellation flow in order to meet this requirement.
> As result we should have one or few tickets to implementation, potentially it will required some documents with describe the current state and proposed changes to have final state.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)