[ https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16057991#comment-16057991 ]
ASF GitHub Bot commented on DRILL-3640: --------------------------------------- Github user kkhatua commented on a diff in the pull request: https://github.com/apache/drill/pull/858#discussion_r123330684 --- Diff: exec/jdbc/src/main/java/org/apache/drill/jdbc/impl/DrillStatementImpl.java --- @@ -422,6 +507,9 @@ public ResultSet getGeneratedKeys() throws SQLException { public int executeUpdate(String sql, int autoGeneratedKeys) throws SQLException { throwIfClosed(); try { + if (timeoutTrigger != null) { --- End diff -- I'm submit the timeout trigger to the pool and counting on that trigger doing a query cancellation to do that. I don't think Drill supports executeUpdate, but as long as a query cancellation for updates does the rollback of the transaction, this should suffice. This worked well for large queries where the execute###() call was longer than the timeout period and allowed for the cancellation to do the interrupt. > 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.11.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)