You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Attila Doroszlai (Jira)" <ji...@apache.org> on 2022/09/30 11:27:00 UTC
[jira] [Updated] (HIVE-26579) Prepare for Hadoop switching to Reload4j
[ https://issues.apache.org/jira/browse/HIVE-26579?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Attila Doroszlai updated HIVE-26579:
------------------------------------
Description:
Hadoop moved from Log4j1 to Reload4j (HADOOP-18088). The goal of this task is to prepare Hive for that change:
* Hive build fails with current {{useStrictFiltering=true}} setting in some assemblies, due to excluded dependency (log4j) not really being present.
* Exclude {{ch.qos.reload4j:\*}} in addition to current {{log4j:*}} to avoid polluting the assemblies and shaded jars.
was:
Hadoop moved from Log4j1 to Reload4j (HADOOP-18088). The goal of this task is to prepare Hive for that change:
* Hive build fails with current {{useStrictFiltering=true}} setting in some assemblies, due to excluded dependency (log4j) not really being present.
* Exclude {{ch.qos.reload4j:*}} in addition to current {{log4j:*}} to avoid polluting the assemblies and shaded jars.
> Prepare for Hadoop switching to Reload4j
> ----------------------------------------
>
> Key: HIVE-26579
> URL: https://issues.apache.org/jira/browse/HIVE-26579
> Project: Hive
> Issue Type: Task
> Components: Build Infrastructure
> Reporter: Attila Doroszlai
> Assignee: Attila Doroszlai
> Priority: Major
>
> Hadoop moved from Log4j1 to Reload4j (HADOOP-18088). The goal of this task is to prepare Hive for that change:
> * Hive build fails with current {{useStrictFiltering=true}} setting in some assemblies, due to excluded dependency (log4j) not really being present.
> * Exclude {{ch.qos.reload4j:\*}} in addition to current {{log4j:*}} to avoid polluting the assemblies and shaded jars.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)