You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2026/01/28 10:21:00 UTC
[jira] [Created] (IGNITE-27679) Sql. SelectCount plan is affected by consequent DML in script
Konstantin Orlov created IGNITE-27679:
-----------------------------------------
Summary: Sql. SelectCount plan is affected by consequent DML in script
Key: IGNITE-27679
URL: https://issues.apache.org/jira/browse/IGNITE-27679
Project: Ignite
Issue Type: Bug
Components: sql ai3
Affects Versions: 3.1
Reporter: Konstantin Orlov
Take a look at script below:
{code}
CREATE TABLE integers (i INT PRIMARY KEY);
INSERT INTO integers SELECT * FROM TABLE(system_range(1, 1000));
SELECT count(*) FROM integers;
DELETE FROM integers;
{code}
Initially, {{SELECT count(*)}} was not affected by consequent {{DELETE}} statement because it was executed in fair RO transaction. But after optimization introduced in IGNITE-22829 this invariant was broken as now, if aforementioned optimization is applied, the execution follows short path avoiding creation of transaction.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)