]
Steven Hawkins resolved TEIID-3781.
-----------------------------------
Fix Version/s: 8.12.1
8.13
Resolution: Done
The general issue here is that the cancellation is not propagated deeply into the plan.
Now the context and child contexts are notified and checked on each batch operation.
Queries are not killed even if the client sends a cancel request
----------------------------------------------------------------
Key: TEIID-3781
URL:
https://issues.jboss.org/browse/TEIID-3781
Project: Teiid
Issue Type: Bug
Reporter: Salvatore R
Assignee: Steven Hawkins
Fix For: 8.12.1, 8.13
I have different behaviors when I try to cancel the following queries:
{code:sql}
SELECT COUNT(*)
FROM
(SELECT * FROM my.address) as x1,
(SELECT * FROM my.address) as y1
{code}
and
{code:sql}
SELECT COUNT(*)
FROM
(SELECT * FROM my.address limit 10000) as x1,
(SELECT * FROM my.address limit 10000) as y1
{code}
where "my.address" is a table with around 20000 rows in MySQL.
The first query is immediately cancelled but the second one continues to run until the
end and it is never killed.
Looking at the generated plans, the main difference is that the first query is fully
pushed down to MySQL while the second one is not.