[
https://issues.apache.org/jira/browse/HIVE-25824?focusedWorklogId=730203&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-730203
]
ASF GitHub Bot logged work on HIVE-25824:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Feb/22 04:02
Start Date: 21/Feb/22 04:02
Worklog Time Spent: 10m
Work Description: vrao91 commented on pull request #2908:
URL: https://github.com/apache/hive/pull/2908#issuecomment-1046449974
When checking the version of hive, it's still showing 2.3.6.
```
bin/hive --version
Hive 2.3.6-amzn-0
Git
git://<ip-address>/workspace/workspace/bigtop.release-rpm-5.28.1/build/hive/rpm/BUILD/apache-hive-2.3.6-amzn-0-src
-r a3b61461af0d6b4d981c915b0a1f342464987aaa
Compiled by ec2-user on Sat Dec 14 09:17:06 UTC 2019
From source with checksum 308f8d79fe62254ef0c65ed73f5847ca
```
Any ideas?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 730203)
Time Spent: 2.5h (was: 2h 20m)
> Upgrade branch-2.3 to log4j 2.17.0
> ----------------------------------
>
> Key: HIVE-25824
> URL: https://issues.apache.org/jira/browse/HIVE-25824
> Project: Hive
> Issue Type: Improvement
> Affects Versions: 2.3.8
> Reporter: Luca Toscano
> Assignee: Luca Toscano
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.3.10
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> Hi everybody,
> I am wondering if there are any plans to upgrade branch-2.3 to log4j 2.17.0
> as it was done in HIVE-25795 (and related).
> In Apache Bigtop we created https://github.com/apache/bigtop/pull/844, since
> the one before the last release (Bigtop 1.5.0) shipped Hive 2.3.6.
> I can try to file a pull request for branch-2.3 adapting what was done for
> Bigtop (if the branch is still maintained), but I am currently experiencing
> some mvn package failures (that seem unrelated to log4j) so I'd need some
> help for you in case :)
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
