You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (Jira)" <ji...@apache.org> on 2020/01/23 15:58:00 UTC

[jira] [Resolved] (DRILL-6738) validationQuery option for JDBC storage plugin

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

Arina Ielchiieva resolved DRILL-6738.
-------------------------------------
    Resolution: Fixed

Merged into master with commit id 50cd931da0364355535029db8e9d7a1445218803.

> validationQuery option for JDBC storage plugin
> ----------------------------------------------
>
>                 Key: DRILL-6738
>                 URL: https://issues.apache.org/jira/browse/DRILL-6738
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Storage - JDBC
>    Affects Versions: 1.14.0
>         Environment: Apache Drill version 1.14.0 running on CentOS 7.0.1406.
> MySQL version 5.5.43 running on CentOS 6.4.
> MySQL connector/j version 5.1.44.
>            Reporter: Cheolgoo Kang
>            Assignee: Arina Ielchiieva
>            Priority: Major
>             Fix For: 1.18.0
>
>
> Currently JDBC storage plugin uses DBCP2 for the connection pooling, but it wouldn't validate the connection's still available or not, and it'd just spit the connection lost error.
> We should be able to have a validationQuery option described [here|https://commons.apache.org/proper/commons-dbcp/configuration.html] in Drill's JDBC storage plugin configuration.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)