[
https://issues.apache.org/jira/browse/IGNITE-26143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin resolved IGNITE-26143.
---------------------------------------
Resolution: Invalid
> Sql. Jdbc. Migrate Statement.executeBatch() to use thin client SQL API
> -----------------------------------------------------------------------
>
> Key: IGNITE-26143
> URL: https://issues.apache.org/jira/browse/IGNITE-26143
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc ai3, sql ai3
> Reporter: Pavel Pereslegin
> Priority: Major
> Labels: ignite-3
>
> We need to migrate Statement.executeBatch() to use thin client SQL API
> Statement.executeBatch() is just a batch of DML/DDL queries without dynamic
> parameters.
> {code:java}
> /** Batch. */
> private List<String> batch;
> {code}
> We don't have similar API operation, but we can batch of queries into a
> script, execute and collect update counters on the client side.
> IgniteSql.executeScript cannot be used for this - we need to use internal API
> implemented in IGNITE-26087 for this.
> It will also be necessary to support the following:
> 1. Cancellation token (see how it is done in IGNITE-26139)
> 2. Pass client time zone (see
> JdbcConnection.connectionProperties().getConnectionTimeZone) as statement
> properties.
> 3. Pass transaction in non-autocommit mode (see how it is done in
> IGNITE-26139)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
