[
https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242666#comment-16242666
]
ASF GitHub Bot commented on DRILL-3640:
---------------------------------------
Github user kkhatua commented on a diff in the pull request:
https://github.com/apache/drill/pull/1024#discussion_r149472806
--- Diff:
exec/jdbc/src/main/java/org/apache/drill/jdbc/impl/DrillPreparedStatementImpl.java
---
@@ -61,8 +65,14 @@ protected DrillPreparedStatementImpl(DrillConnectionImpl
connection,
if (preparedStatementHandle != null) {
((DrillColumnMetaDataList)
signature.columns).updateColumnMetaData(preparedStatementHandle.getColumnsList());
}
+ //Implicit query timeout
+ this.queryTimeoutInSeconds = 0;
+ this.elapsedTimer = Stopwatch.createUnstarted();
--- End diff --
I thought the Statement and Cursor had a 1:1 relationship, so they can
share the timer. I guess for a PreparedStatement I cannot make that assumption.
Will fix this. +1
> Drill JDBC driver support Statement.setQueryTimeout(int)
> --------------------------------------------------------
>
> Key: DRILL-3640
> URL: https://issues.apache.org/jira/browse/DRILL-3640
> Project: Apache Drill
> Issue Type: New Feature
> Components: Client - JDBC
> Affects Versions: 1.2.0
> Reporter: Chun Chang
> Assignee: Kunal Khatua
> Fix For: 1.12.0
>
>
> It would be nice if we have this implemented. Run away queries can be
> automatically canceled by setting the timeout.
> java.sql.SQLFeatureNotSupportedException: Setting network timeout is not
> supported.
> at
> org.apache.drill.jdbc.impl.DrillStatementImpl.setQueryTimeout(DrillStatementImpl.java:152)
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
