[
https://issues.apache.org/jira/browse/IGNITE-10304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aleksey Plekhanov updated IGNITE-10304:
---------------------------------------
Fix Version/s: (was: 2.9)
> SQL: Encapsulate H2 query execution into ConnectionManager
> ----------------------------------------------------------
>
> Key: IGNITE-10304
> URL: https://issues.apache.org/jira/browse/IGNITE-10304
> Project: Ignite
> Issue Type: Task
> Components: sql
> Reporter: Vladimir Ozerov
> Priority: Major
>
> This ticket should be done after IGNITE-10299. Currently
> {{ConnectionManager}} exposes cached H2 connections to the outside. Sometimes
> these connections are used in safe manner and
> {{ConnectionManager.onSqlException}} is called to recycle bad connection. But
> most of the time this is not the case, what may lead to unexpected behavior.
> Let's try to hide all statement execution logic inside {{ConnectionManager}}
> to avoid this.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
