[
https://issues.apache.org/jira/browse/IGNITE-16276?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantin Orlov updated IGNITE-16276:
--------------------------------------
Description:
As for now, the script like below returns an empty result sets for both SELECT
queries. I believe this behaviour is counterintuitive and should be revised.
{code:sql}
drop table if exists test;
create table test(ID int primary key, NAME varchar(20));
insert into test (ID, NAME) values (0, 'name_0');
select * from test where id < 1;
insert into test (ID, NAME) values (2, 'name_2');
select * from test where id < 3;
{code}
The root cause of such behaviour is that the execution of the local fragments
starts as soon as the very first row will be requested from the cursor. Whereas
for remote fragments the execution starts immediately after receiving a
QueryStartRequest.
was:
As for now, the script like below returns an empty result sets for both SELECT
queries. I believe this behaviour is counterintuitive and should be revised.
{code:sql}
drop table if exists test;
create table test(ID int primary key, NAME varchar(20));
insert into test (ID, NAME) values (0, 'name_0');
select * from test where id < 1;
insert into test (ID, NAME) values (2, 'name_2');
select * from test where id < 3;
{code}
The root cause of such behavior is that the execution of the local fragments
starts as soon as the very first row will be requested from the cursor. Whereas
for remote fragments the execution starts immediately after receiving a
QueryStartRequest.
> Sql. Revise execution of multi statement queries
> ------------------------------------------------
>
> Key: IGNITE-16276
> URL: https://issues.apache.org/jira/browse/IGNITE-16276
> Project: Ignite
> Issue Type: Bug
> Components: sql
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> As for now, the script like below returns an empty result sets for both
> SELECT queries. I believe this behaviour is counterintuitive and should be
> revised.
> {code:sql}
> drop table if exists test;
> create table test(ID int primary key, NAME varchar(20));
> insert into test (ID, NAME) values (0, 'name_0');
> select * from test where id < 1;
> insert into test (ID, NAME) values (2, 'name_2');
> select * from test where id < 3;
> {code}
> The root cause of such behaviour is that the execution of the local fragments
> starts as soon as the very first row will be requested from the cursor.
> Whereas for remote fragments the execution starts immediately after receiving
> a QueryStartRequest.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
