You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "YuXiang Zhuang (Jira)" <ji...@apache.org> on 2025/02/27 07:43:00 UTC
[jira] [Updated] (HIVE-28791) Add JDBC parameter to configure loginTimeout separately from socketTimeout
[ https://issues.apache.org/jira/browse/HIVE-28791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
YuXiang Zhuang updated HIVE-28791:
----------------------------------
Description:
Currently, the Hive JDBC driver lacks a dedicated parameter to set the {{loginTimeout}} for connection establishment. The driver implicitly uses the {{socketTimeout}} value for both the login phase and subsequent socket operations. This creates ambiguity and limits users' ability to handle connection establishment failures gracefully.
was:Currently, the Hive JDBC driver lacks a dedicated parameter to set the {{loginTimeout}} for connection establishment. The driver implicitly uses the {{socketTimeout}} value for both the login phase and subsequent socket operations. This creates ambiguity and limits users' ability to handle connection establishment failures gracefully.
> Add JDBC parameter to configure loginTimeout separately from socketTimeout
> --------------------------------------------------------------------------
>
> Key: HIVE-28791
> URL: https://issues.apache.org/jira/browse/HIVE-28791
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 4.0.1
> Reporter: YuXiang Zhuang
> Priority: Major
>
> Currently, the Hive JDBC driver lacks a dedicated parameter to set the {{loginTimeout}} for connection establishment. The driver implicitly uses the {{socketTimeout}} value for both the login phase and subsequent socket operations. This creates ambiguity and limits users' ability to handle connection establishment failures gracefully.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)