[
https://issues.apache.org/jira/browse/HIVE-4924?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038621#comment-14038621
]
Thorsten Meinl commented on HIVE-4924:
--------------------------------------
Any news on this? Currently the timeout for the Socket created by thrift is
taken from the login (!) timeout set by the java.sql.DriverManager. First of
all nobody expects the login timeout to affect the read timeout during a query
and secondly this timeout can only be set globally for the whole JVM. This
means if you have connections to other databases they will also be affected
when the value is changed.
> Support query timeout for jdbc2
> -------------------------------
>
> Key: HIVE-4924
> URL: https://issues.apache.org/jira/browse/HIVE-4924
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2, JDBC
> Reporter: Navis
> Assignee: Navis
> Priority: Trivial
> Attachments: HIVE-4924.D11787.1.patch, HIVE-4924.D11787.2.patch
>
>
> support
> {code}
> Statement.setQueryTimeout(int timeout)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
