[
https://issues.apache.org/jira/browse/HIVE-27132?focusedWorklogId=850280&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-850280
]
ASF GitHub Bot logged work on HIVE-27132:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 10/Mar/23 09:51
Start Date: 10/Mar/23 09:51
Worklog Time Spent: 10m
Work Description: shalk opened a new pull request, #4107:
URL: https://github.com/apache/hive/pull/4107
<!--
Thanks for sending a pull request! Here are some tips for you:
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/Hive/HowToContribute
2. Ensure that you have created an issue on the Hive project JIRA:
https://issues.apache.org/jira/projects/HIVE/summary
3. Ensure you have added or run the appropriate tests for your PR:
4. If the PR is unfinished, add '[WIP]' in your PR title, e.g.,
'[WIP]HIVE-XXXXX: Your PR title ...'.
5. Be sure to keep the PR description updated to reflect all changes.
6. Please write your PR title to summarize what this PR proposes.
7. If possible, provide a concise example to reproduce the issue for a
faster review.
-->
### What changes were proposed in this pull request?
this is backport from https://github.com/apache/hive/pull/1611 HIVE-12371
background:
DriverManager.loginTimeout effect hive-jdbc 3.1.x's timeout， this is a
global value。
We use HikariCP in our app， every time HikariCP alway [set the global value
to 30s]
(https://github.com/brettwooldridge/HikariCP/blob/dev/src/main/java/com/zaxxer/hikari/util/DriverDataSource.java#L155).
So we can not use `hikariCP with mysql` and `hive-jdbc` in different
timeout.
### Why are the changes needed?
<!--
Please clarify why the changes are needed. For instance,
1. If you propose a new API, clarify the use case for a new API.
2. If you fix a bug, you can clarify why it is a bug.
-->
### Does this PR introduce _any_ user-facing change?
<!--
Note that it means *any* user-facing change including all aspects such as
the documentation fix.
If yes, please clarify the previous behavior and the change this PR proposes
- provide the console output, description, screenshot and/or a reproducable
example to show the behavior difference if possible.
If possible, please also clarify if this is a user-facing change compared to
the released Hive versions or within the unreleased branches such as master.
If no, write 'No'.
-->
### How was this patch tested?
<!--
If tests were added, say they were added here. Please make sure to add some
test cases that check the changes thoroughly including negative and positive
cases if possible.
If it was tested in a way different from regular unit tests, please clarify
how you tested step by step, ideally copy and paste-able, so that other
reviewers can test and check, and descendants can verify in the future.
If tests were not added, please describe why they were not added and/or why
it was difficult to add.
-->
Issue Time Tracking
-------------------
Worklog Id: (was: 850280)
Remaining Estimate: 0h
Time Spent: 10m
> backport HIVE-12371 to branch-3 hive-jdbc use global Driver loginTimeout
> ------------------------------------------------------------------------
>
> Key: HIVE-27132
> URL: https://issues.apache.org/jira/browse/HIVE-27132
> Project: Hive
> Issue Type: Improvement
> Components: JDBC
> Reporter: shalk
> Priority: Major
> Fix For: 3.2.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> when i use hive jdbc 3.1.3 , meet the problem hive-jdbc use global
> Driver.loginTimeout
> Though the problem have solve by HIVE-12371 on branch 4.x, so i want to
> backport it on open source branch
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
