[
https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16070517#comment-16070517
]
ASF GitHub Bot commented on DRILL-3640:
---------------------------------------
Github user laurentgo commented on the issue:
https://github.com/apache/drill/pull/858
As for System.currentTimeMillis(), maybe not as expensive as you think: if
I remember correctly, it's a JVM intrinsic (no JNI cost), and if mapped to
gettimeofday (which I believe is the case), it's a VSDO function on Linux,
which means it's pretty cheap (no user/kernel context change). Compared to
creating threads, and waiting on conditions, should be way cheaper.
> 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)
