[
https://issues.apache.org/jira/browse/CALCITE-2301?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16467169#comment-16467169
]
Fan Yang commented on CALCITE-2301:
-----------------------------------
I think users would set the query timeout using
CalciteStatement.setQueryTimeout(), implemented in
[https://github.com/apache/calcite-avatica/blob/master/core/src/main/java/org/apache/calcite/avatica/AvaticaStatement.java#L318]
By removing the query timeout restriction inside Calcite, we can make sure that
CalciteStatement.setQueryTimeout() will do what it is supposed to do.
> Remove the 10-second-timeout restriction in ResultSetEnumerable
> ---------------------------------------------------------------
>
> 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
> 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)
