[
https://issues.apache.org/jira/browse/IGNITE-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-20443:
--------------------------------------
Description:
We need to add a new method to {{QueryProcessor}} that will be responsible for
processing multi-statement queries.
{{// TBD suggested method signature}}
In general, statements must be executed one by one in the order they are
specified in the script.
{{// TBD suggestion for parsing}}
Due to the lazy nature of SQL engine, the moment when the current statement is
"complete" depends on the user who drains the cursor.
To avoid dependency on a user's actions, it proposed to consider statement
being "complete" as soon as first page is ready to be returned to the user.
{{// TBD reference to ticket about SqlCursor event}}
was:
We need to add a new method to {{QueryProcessor}} that will be responsible for
processing multistatements query.
{{// TBD suggested method signature}}
In general, statements must be executed one by one in the order they are
specified in the script.
{{// TBD suggestion for parsing}}
Due to the lazy nature of SQL engine, the moment when the current statement is
"complete" depends on the user who drains the cursor.
To avoid dependency on a user's actions, it proposed to consider statement
being "complete" as soon as first page is ready to be returned to the user.
{{// TBD reference to ticket about SqlCursor event}}
> Sql. Implement script processing logic.
> ---------------------------------------
>
> Key: IGNITE-20443
> URL: https://issues.apache.org/jira/browse/IGNITE-20443
> Project: Ignite
> Issue Type: Improvement
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> We need to add a new method to {{QueryProcessor}} that will be responsible
> for processing multi-statement queries.
> {{// TBD suggested method signature}}
> In general, statements must be executed one by one in the order they are
> specified in the script.
> {{// TBD suggestion for parsing}}
> Due to the lazy nature of SQL engine, the moment when the current statement
> is "complete" depends on the user who drains the cursor.
> To avoid dependency on a user's actions, it proposed to consider statement
> being "complete" as soon as first page is ready to be returned to the user.
> {{// TBD reference to ticket about SqlCursor event}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
