You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2018/11/16 17:16:00 UTC

[jira] [Created] (IGNITE-10304) SQL: Encapsulate H2 query execution into ConnectionManager

Vladimir Ozerov created IGNITE-10304:
----------------------------------------

             Summary: 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
             Fix For: 2.8


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
(v7.6.3#76005)