[
https://issues.apache.org/jira/browse/IGNITE-26139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin updated IGNITE-26139:
--------------------------------------
Summary: Sql. Jdbc. Support non-autocommit mode and cancellation token for
use in thin client API. (was: Sql. Jdbc. Migrate Statement.executeUpdate() to
use thin client SQL API)
> 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
>
> We need to (re-)implement Statement.executeUpdate using ClientSql (internal)
> API .
> After IGNITE-26086 internal API to execute query with specified query type
> should be implemented.
> executeUpdate() must use this API to execute query (query type = DML/DDL).
> It will also be necessary to support the following:
> 1. Cancellation token (to be able cancel query)
> 2. Pass client time zone (see
> JdbcConnection.connectionProperties().getConnectionTimeZone) as statement
> property.
> 3. Pass transaction if autocommit=false mode (similar to what we have on
> server side - we need to lazily start transaction
> (client.transactions().begin() and save it inside JdbcConnection) if it isn't
> started yet)
> Note: it is expected that this task doesn't include JdbcResultSet modification
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
