You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Cheolgoo Kang (JIRA)" <ji...@apache.org> on 2018/09/10 17:04:00 UTC
[jira] [Updated] (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 ]
Cheolgoo Kang updated DRILL-6738:
---------------------------------
Description:
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.
was:
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 in [here|https://commons.apache.org/proper/commons-dbcp/configuration.html] in Drill's JDBC storage plugin configuration.
> 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
> Priority: Major
>
> 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
(v7.6.3#76005)