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

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

                Author: ASF GitHub Bot
            Created on: 06/Apr/23 17:31
            Start Date: 06/Apr/23 17:31
    Worklog Time Spent: 10m 
      Work Description: amanraj2520 commented on PR #4203:
URL: https://github.com/apache/hive/pull/4203#issuecomment-1499398840

   I agree with you that this needs to be upgraded in standalone-metastore 
also. This ticket is specifically created to match the exact backport of the 
dependency upgrade that happened in HIVE-3.1.3 release. This PR cherry-picks 
the exact commit that went into branch-3.1.
   
   @Aggarwal-Raghav Answering your question, there was this commit that 
happened in branch-3.1 (Hive-3.1.3) after this commit which upgraded log4j2 in 
standalone-metastore - 1eda74d7. I don't think we should raise a separate 
ticket for commons-lang3 if this ticket address that upgrade as well as this is 
in sync with branch-3.1
   
   @apoorvaagg We can cherry pick this commit as well in this ticket. That 
would ensure that we are perfectly in sync with branch-3.1 cherry-picks.




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

    Worklog Id:     (was: 855357)
    Time Spent: 0.5h  (was: 20m)

>  Backport Upgrade commons,httpclient,jackson,jetty,log4j binaries from 
> branch-3.1
> ---------------------------------------------------------------------------------
>
>                 Key: HIVE-27220
>                 URL: https://issues.apache.org/jira/browse/HIVE-27220
>             Project: Hive
>          Issue Type: Sub-task
>            Reporter: Apoorva Aggarwal
>            Assignee: Apoorva Aggarwal
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.2.0
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>




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

Reply via email to