[
https://issues.apache.org/jira/browse/HIVE-12371?focusedWorklogId=553109&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-553109
]
ASF GitHub Bot logged work on HIVE-12371:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Feb/21 17:54
Start Date: 16/Feb/21 17:54
Worklog Time Spent: 10m
Work Description: prasanthj merged pull request #1611:
URL: https://github.com/apache/hive/pull/1611
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 553109)
Time Spent: 2h 20m (was: 2h 10m)
> Adding a timeout connection parameter for JDBC
> ----------------------------------------------
>
> Key: HIVE-12371
> URL: https://issues.apache.org/jira/browse/HIVE-12371
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Reporter: Nemon Lou
> Assignee: Xi Chen
> Priority: Minor
> Labels: pull-request-available
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> There are some timeout settings from server side:
> HIVE-4766
> HIVE-6679
> Adding a timeout connection parameter for JDBC is useful in some scenario:
> 1,beeline (which can not set timeout manually)
> 2,customize timeout for different connections (among hive or RDBs,which can
> not be done via DriverManager.setLoginTimeout())
> Just like postgresql,
> {noformat}
> jdbc:postgresql://localhost/test?user=fred&password=secret&ssl=true&connectTimeout=0
> {noformat}
> or mysql
> {noformat}
> jdbc:mysql://xxx.xx.xxx.xxx:3306/database?connectTimeout=60000&socketTimeout=60000
> {noformat}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
