Cheng Pan created HIVE-26336:
--------------------------------
Summary: 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
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)
