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

Vladimir Sitnikov commented on CALCITE-2301:
--------------------------------------------

[~julianhyde], I've updated the code to use existing 
\{{org.apache.calcite.DataContext.Variable#UTC_TIMESTAMP}} which should 
designate "query start timestamp".

Testcase is not that trivial: HSQLDB does not have builtin {{sleep}} function. 
I can add a test for PostgreSQL (it has pg_sleep), however I'm not that sure 
running tests against PostgreSQL happens often.

> JDBC adapter: use query timeout from the top-level statement
> ------------------------------------------------------------
>
>                 Key: CALCITE-2301
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2301
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.16.0
>            Reporter: Fan Yang
>            Assignee: Julian Hyde
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: next
>
>
> It's not a good idea to have the magic number here. Also, databases may not 
> get back within 10 second for various reasons (e.g., in the case of JDBC 
> schema).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to