[
https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16271773#comment-16271773
]
ASF GitHub Bot commented on DRILL-3640:
---------------------------------------
Github user kkhatua commented on the issue:
https://github.com/apache/drill/pull/1024
@laurentgo
I've added server-triggered timeout tests and made other changes as well,
but they require support for
[DRILL-5973](https://issues.apache.org/jira/browse/DRILL-5973) . I tested this
commit (#1024 ) as a cherry pick on top of that PR's commit (#1055) and I was
able to simulate the server-induced timeout.
Will need a +1 for that PR before I can enable the tests here.
For now, I've marked these tests as `@ignore` to ensure that the remaining
tests pass and the feature works as intended.
Can you review them both (this and #1055 )?
> Drill JDBC driver support Statement.setQueryTimeout(int)
> --------------------------------------------------------
>
> Key: DRILL-3640
> URL: https://issues.apache.org/jira/browse/DRILL-3640
> Project: Apache Drill
> Issue Type: Improvement
> Components: Client - JDBC
> Affects Versions: 1.2.0
> Reporter: Chun Chang
> Assignee: Kunal Khatua
> Fix For: 1.13.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)
