[
https://issues.apache.org/jira/browse/HIVE-25824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17470505#comment-17470505
]
Luca Toscano commented on HIVE-25824:
-------------------------------------
[~csun] Hi! If you have time to help: for some reason I end up in a a
no-class-def issue with the new patch (while testing 2.3.6 in some
environments) - https://issues.apache.org/jira/browse/BIGTOP-3619
I am still not able to reproduce with the Apache Bigtop's testing Docker
images, any suggestion? I checked the datanucleus jars, they are there and they
contain the .class files needed (I also checked that they are included in the
Hive metastore's classpath inspecting the STARTUP_MSG log).
> 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
> Priority: Major
> Labels: pull-request-available
> Time Spent: 1h
> 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)
