[
https://issues.apache.org/jira/browse/IGNITE-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-26139:
--------------------------------------
Description:
*NOTE*: this is a preparation step for migrating current JDBC driver
implementation to use thin client SQL API, but the old code for jdbc-managed
transaction (and cancellation correlation token) should not be removed, because
it is still used by current implementation).
Requirements:
# Support non-autocommit mode using thin client transactions API.
# Support cancellation token using thin client API.
Basically what we need to do is the following:
# 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.
was:
Requirements:
# Support non-autocommit mode using thin client transactions API.
# Support cancellation token using thin client API.
Basically what we need to do is the following:
1. When executing a query, if autocommit=false and the transaction is not
started - start a new transaction and save it in the JdbcConnection
2. JdbcConnection - commit/rollback should commit/rollback this tx.
3. 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.
Note: this is a preparation step for migrating current JDBC driver
implementation to use thin client SQL API, but the old code for jdbc-managed
transaction (and cancellation correlation token) should not be removed, because
it is still used by current implementation.
> 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
> Priority: Major
> Labels: ignite-3
>
> *NOTE*: this is a preparation step for migrating current JDBC driver
> implementation to use thin client SQL API, but the old code for jdbc-managed
> transaction (and cancellation correlation token) should not be removed,
> because it is still used by current implementation).
> Requirements:
> # Support non-autocommit mode using thin client transactions API.
> # Support cancellation token using thin client API.
> Basically what we need to do is the following:
> # 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)
