[
https://issues.apache.org/jira/browse/IGNITE-18984?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Yury Gerzhedovich updated IGNITE-18984:
---------------------------------------
Description:
After IGNITE-18983, the next part is a migration of batched methods
(*Statement#executeBatch). Here we need to replace call to
{{QueryProcessor#queryAsync}} with {{{}QueryProcessor#querySingleAsync{}}}.
NB: need to not forget about session recovery; depending on implementation
introduced in IGNITE-18983, it may or may not require explicit handling..
was:
After IGNITE-18983, the next part is a migration of batched methods
(*Statement#executeBatch). Here we need to replace call to
{{QueryProcessor#queryAsync}} with {{{}QueryProcessor#querySingleAsync{}}}.
NB: need to not forget about session recovery; depending on implementation
introduced in IGNITE-18983, it may or may not require explicit handling.
> Sql. Jdbc. Migrate batched methods on new internal API
> ------------------------------------------------------
>
> Key: IGNITE-18984
> URL: https://issues.apache.org/jira/browse/IGNITE-18984
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> After IGNITE-18983, the next part is a migration of batched methods
> (*Statement#executeBatch). Here we need to replace call to
> {{QueryProcessor#queryAsync}} with {{{}QueryProcessor#querySingleAsync{}}}.
> NB: need to not forget about session recovery; depending on implementation
> introduced in IGNITE-18983, it may or may not require explicit handling..
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
