[ 
https://issues.apache.org/jira/browse/DRILL-3640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16243133#comment-16243133
 ] 

ASF GitHub Bot commented on DRILL-3640:
---------------------------------------

Github user laurentgo commented on a diff in the pull request:

    https://github.com/apache/drill/pull/1024#discussion_r149543078
  
    --- Diff: 
exec/jdbc/src/main/java/org/apache/drill/jdbc/impl/DrillCursor.java ---
    @@ -333,8 +368,14 @@ void close() {
         final int batchQueueThrottlingThreshold =
             client.getConfig().getInt(
                 ExecConstants.JDBC_BATCH_QUEUE_THROTTLING_THRESHOLD );
    -    resultsListener = new ResultsListener(batchQueueThrottlingThreshold);
    +    resultsListener = new ResultsListener(this, 
batchQueueThrottlingThreshold);
         currentBatchHolder = new RecordBatchLoader(client.getAllocator());
    +    try {
    +      setTimeout(this.statement.getQueryTimeout());
    +    } catch (SQLException e) {
    +      // Printing any unexpected SQLException stack trace
    +      e.printStackTrace();
    --- End diff --
    
    two choices here:
    - we don't think it's important if we cannot get the value, so we should 
log it properly and not simply dump the exception
    - we think this is important, and we propagate the exception to the caller
    
    (I think it is important: the most likely reason why we could not get the 
value if that the statement was closed, and we should probably notify the user 
about it).


> 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)

Reply via email to