[
https://issues.apache.org/jira/browse/HIVE-26336?focusedWorklogId=783288&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-783288
]
ASF GitHub Bot logged work on HIVE-26336:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Jun/22 09:42
Start Date: 21/Jun/22 09:42
Worklog Time Spent: 10m
Work Description: pan3793 commented on PR #3379:
URL: https://github.com/apache/hive/pull/3379#issuecomment-1161512614
Let me try to add a unit test. (Not sure if easy because it's
network-related)
Issue Time Tracking
-------------------
Worklog Id: (was: 783288)
Time Spent: 1h (was: 50m)
> Hive JDBC Driver should respect JDBC DriverManager#loginTimeout
> ---------------------------------------------------------------
>
> Key: HIVE-26336
> URL: https://issues.apache.org/jira/browse/HIVE-26336
> Project: Hive
> Issue Type: Bug
> Components: JDBC
> Affects Versions: 4.0.0-alpha-1
> Reporter: Cheng Pan
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> Remaining Estimate: 0h
>
> Before HIVE-12371, the Hive JDBC Driver uses DriverManager#loginTimeout as
> both connectTimeout and socketTimeout, which usually cause socket timeout
> exceptions for users who use Hive JDBC Driver in Spring Boot project, because
> Spring Boot will setLoginTimeout to 30s (default values).
> HIVE-12371 introduced a new parameter socketTimeout, and does not care about
> DriverManager#loginTimeout anymore, I think it's not a correct solution.
> I think the for loginTimeout, prefer to use loginTimeout (in milliseconds)
> from jdbc connection url, and fallback to use DriverManger#getLoginTimeout
> (in seconds).
> For socketTimeout, use socketTimeout (in milliseconds) from jdbc connection
> url if present.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
