You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Pavel Pereslegin (Jira)" <ji...@apache.org> on 2023/09/19 13:21:00 UTC
[jira] [Updated] (IGNITE-20443) Sql. Implement script processing logic.
[ https://issues.apache.org/jira/browse/IGNITE-20443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pavel Pereslegin updated IGNITE-20443:
--------------------------------------
Description:
Design document: https://docs.google.com/document/d/1M0dEGl84CBmT5wjJ6ca5Ya7U3I40vMyHGrU2QQtb5hU/edit
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
was:
Design document: https://docs.google.com/document/d/1M0dEGl84CBmT5wjJ6ca5Ya7U3I40vMyHGrU2QQtb5hU/edit
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 suggested 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: Task
> Components: sql
> Reporter: Pavel Pereslegin
> Priority: Major
>
> Design document: https://docs.google.com/document/d/1M0dEGl84CBmT5wjJ6ca5Ya7U3I40vMyHGrU2QQtb5hU/edit
> 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
--
This message was sent by Atlassian Jira
(v8.20.10#820010)