You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Maksim Zhuravkov (Jira)" <ji...@apache.org> on 2025/10/07 09:03:00 UTC
[jira] [Assigned] (IGNITE-26139) Sql. Jdbc. Support non-autocommit mode and cancellation token for use in thin client API.
[ https://issues.apache.org/jira/browse/IGNITE-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maksim Zhuravkov reassigned IGNITE-26139:
-----------------------------------------
Assignee: Maksim Zhuravkov
> Sql. Jdbc. Support non-autocommit mode and cancellation token for use in thin client API.
> -----------------------------------------------------------------------------------------
>
> Key: IGNITE-26139
> URL: https://issues.apache.org/jira/browse/IGNITE-26139
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc ai3, sql ai3
> Reporter: Pavel Pereslegin
> Assignee: Maksim Zhuravkov
> Priority: Major
> Labels: ignite-3
>
> Requirements:
> # Support non-autocommit mode using thin client transactions API.
> # Support cancellation token using thin client API.
> How to implement:
> # When executing a query, if autocommit=false and the transaction is not started - start a new transaction and save it in the JdbcConnection
> # JdbcConnection - commit/rollback should commit/rollback this tx.
> # When creating a new statement (JdbcStatement) - we should create CancelHandle (CancelHandle.create()) and save it in statement that will be used to obtain cancellation token for thin client SQL API.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)