[ 
https://issues.apache.org/jira/browse/HIVE-26813?focusedWorklogId=832011&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-832011
 ]

ASF GitHub Bot logged work on HIVE-26813:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 08/Dec/22 10:54
            Start Date: 08/Dec/22 10:54
    Worklog Time Spent: 10m 
      Work Description: zabetak commented on code in PR #3839:
URL: https://github.com/apache/hive/pull/3839#discussion_r1043219960


##########
ql/pom.xml:
##########
@@ -1113,6 +1113,12 @@
                     <exclude>META-INF/licenses/slf4j*/**</exclude>
                   </excludes>
                 </filter>
+                <filter>
+                  <artifact>com.zaxxer:HikariCP</artifact>
+                  <excludes>
+                    <exclude>META-INF/versions/11/module-info.class</exclude>
+                  </excludes>
+                </filter>

Review Comment:
   Makes sense, thanks for the explanation!





Issue Time Tracking
-------------------

    Worklog Id:     (was: 832011)
    Time Spent: 1.5h  (was: 1h 20m)

> Upgrade HikariCP from 2.6.1 to 4.0.3.
> -------------------------------------
>
>                 Key: HIVE-26813
>                 URL: https://issues.apache.org/jira/browse/HIVE-26813
>             Project: Hive
>          Issue Type: Improvement
>          Components: Standalone Metastore
>            Reporter: Chris Nauroth
>            Assignee: Chris Nauroth
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> The Hive Metastore currently integrates with HikariCP 2.6.1 for database 
> connection pooling. This version was released in 2017. The most recent Java 
> 8-compatible release is 4.0.3, released earlier this year. This bug proposes 
> to upgrade so that we can include the past few years of development and bug 
> fixes in the 4.0.0 GA release.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to