[
https://issues.apache.org/jira/browse/IGNITE-23440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-23440:
--------------------------------------
Description:
At the moment we have 3 types of cancelable "entities".
# SQL query
# Transaction
# Compute job
Any of these process can be cancelled (killed) using SQL KILL query.
We need to design and develop a handler API (KillQueryHandler?) that will add
the ability for external components (TransactionManager, IgniteComputeImpl,
etc) to register as a cancellation listener.
Overall, the cancellation of any such "process" consists of the following steps:
* if the process is local - cancel it
* send a message to other cluster nodes to cancel the process
> Provide API for external components to register itself as cancellation
> listener
> -------------------------------------------------------------------------------
>
> Key: IGNITE-23440
> URL: https://issues.apache.org/jira/browse/IGNITE-23440
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> At the moment we have 3 types of cancelable "entities".
> # SQL query
> # Transaction
> # Compute job
> Any of these process can be cancelled (killed) using SQL KILL query.
> We need to design and develop a handler API (KillQueryHandler?) that will
> add the ability for external components (TransactionManager,
> IgniteComputeImpl, etc) to register as a cancellation listener.
> Overall, the cancellation of any such "process" consists of the following
> steps:
> * if the process is local - cancel it
> * send a message to other cluster nodes to cancel the process
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
