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

Posted to issues@drill.apache.org by "James Turton (Jira)" <ji...@apache.org> on 2022/02/11 06:42:00 UTC

[jira] [Closed] (DRILL-8009) DrillConnectionImpl#isValid() doesn't correspond JDBC API

     [ https://issues.apache.org/jira/browse/DRILL-8009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Turton closed DRILL-8009.
-------------------------------

> DrillConnectionImpl#isValid() doesn't correspond JDBC API
> ---------------------------------------------------------
>
>                 Key: DRILL-8009
>                 URL: https://issues.apache.org/jira/browse/DRILL-8009
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - JDBC
>            Reporter: Maksym Rymar
>            Assignee: Maksym Rymar
>            Priority: Major
>             Fix For: 1.20.0
>
>
> {{DrillConnectionImpl#isValid()}} doesn't correspond [Java JDBC API documentation|https://docs.oracle.com/javase/7/docs/api/java/sql/Connection.html#isValid(int)]. Current implementation doesn't do actual connection verify and doesn't cover cases like drillbit termination and network issues.
> {{java.sql.Connection#isValid()}} (which extends {{DrillConnectionImpl}}) widely used in JDBC connection pools like HikariCP and without right implementation, Drill JDBC driver cannot be used with them, because connections will keep alive forever.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)