[
https://issues.apache.org/jira/browse/IGNITE-26087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin reassigned IGNITE-26087:
-----------------------------------------
Assignee: Pavel Pereslegin
> Sql. Implement thin client internal SQL API to support reading script results
> -----------------------------------------------------------------------------
>
> Key: IGNITE-26087
> URL: https://issues.apache.org/jira/browse/IGNITE-26087
> Project: Ignite
> Issue Type: New Feature
> Components: sql ai3
> Reporter: Pavel Pereslegin
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> Currently SQL API over Thin Client supports script execution in a simplified
> form (SQL_EXEC_SCRIPT). Users cannot iterate over the results of the script
> and cannot use an explicit transaction.
> To migrate the JDBC driver to use the SQL API over the thin client, we need
> to extend the thin client's internal API and support iteration over the
> script results.
> * Extend SQL_EXEC operation to pass hasMoreResults flag from server to the
> client (extend ClientAsyncResultSet with hasMoreResults flag).
> * Introduce new operation SQL_CURSOR_NEXT_RESULTSET (similar to
> JDBC_MORE_RESULTS) to allow switching to the next result set of the script.
> Note: the script can be run inside a client transaction (this should work out
> of the box but we should verify this case).
> Public API should not be changed. Tests should use internal API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
