You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Konstantin Orlov (Jira)" <ji...@apache.org> on 2023/03/08 16:58:00 UTC
[jira] [Updated] (IGNITE-18983) Sql. Jdbc. Migrate JDBC handler on new internal API
[ https://issues.apache.org/jira/browse/IGNITE-18983?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Orlov updated IGNITE-18983:
--------------------------------------
Ignite Flags: (was: Docs Required,Release Notes Required)
> Sql. Jdbc. Migrate JDBC handler on new internal API
> ---------------------------------------------------
>
> Key: IGNITE-18983
> URL: https://issues.apache.org/jira/browse/IGNITE-18983
> Project: Ignite
> Issue Type: Improvement
> Components: jdbc
> Reporter: Konstantin Orlov
> Priority: Major
> Labels: ignite-3
>
> h3. Problem
> Currently, JDBC implementation uses old entrypoint to QueryProcessor: {{QueryProcessor#queryAsync(...)}}. It lacks proper integration with transaction, as well as session management.
> As a first step, let's migrate only subset of {{execute*}} methods: {{executeQuery}} and {{executeUpdate}}. Execution of the arbitrary script ({{Statement#execute}}), as well as execution of batched methods ({{*Statement#executeBatch}}) will be addressed in the follow up tickets.
> h3. Implementation notes
> JdbcConnection should created session with the very first request, reuse the same session while it is valid, and recreated the session on the next request if it was invalidated.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)