You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2023/01/25 11:50:00 UTC

[jira] [Updated] (PHOENIX-6862) Phoenix-client jar relocates log4j2

     [ https://issues.apache.org/jira/browse/PHOENIX-6862?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Istvan Toth updated PHOENIX-6862:
---------------------------------
    Description: 
Even though we do not include the log4j2 classes in the shaded phoenix-client JAR, we still relocate org/apache/logging/log4j .

The result is that minicluster cannot start when phoenix-client-embedded is on the classpath (i.e. for PQS)

This only applies for the HBase 2.5 profile.

Exclude log4j2 from the shading config.

  was:
Even though we do not include the log4j2 classes in the shaded phoenix-client JAR, we still relocate org/apache/logging/log4j .

The result is that minicluster cannot start when phoenix-client-embedded is on the classpath (i.e. for PQS)

Exclude log4j2 from the shading config.


> Phoenix-client jar relocates log4j2
> -----------------------------------
>
>                 Key: PHOENIX-6862
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-6862
>             Project: Phoenix
>          Issue Type: Bug
>            Reporter: Istvan Toth
>            Assignee: Istvan Toth
>            Priority: Major
>
> Even though we do not include the log4j2 classes in the shaded phoenix-client JAR, we still relocate org/apache/logging/log4j .
> The result is that minicluster cannot start when phoenix-client-embedded is on the classpath (i.e. for PQS)
> This only applies for the HBase 2.5 profile.
> Exclude log4j2 from the shading config.



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