[
https://issues.apache.org/jira/browse/IGNITE-26810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin closed IGNITE-26810.
-------------------------------------
> Sql. Optimize closing the result of a multi-statement query
> -----------------------------------------------------------
>
> Key: IGNITE-26810
> URL: https://issues.apache.org/jira/browse/IGNITE-26810
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> Consider the following example of a multi-operator query.
> {code:java}
> var stmt = connection.createStatement();
> stmt.execute("SELECT 1; SELECT 2; SELECT 3; SELECT 5;");
> stmt.close();
> {code}
> Statement.close() must close all opened cursors.
> Currently, this is implemented inefficiently, as closing each cursor requires
> 1-2 network requests.
> 1. A request to obtain the next cursor (SQL_CURSOR_NEXT_RESULT_SET) + cursor
> data is fetched on the server side.
> 2. A request (SQL_CURSOR_CLOSE) to close the obtained cursor (if the data
> does not fit on one page).
> We can optimize this operation and do it with a single network request.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
