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

Posted to dev@hbase.apache.org by "Istvan Toth (Jira)" <ji...@apache.org> on 2024/10/02 08:33:00 UTC

[jira] [Resolved] (HBASE-26841) Replace log4j with reload4j for hbase-connector

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

Istvan Toth resolved HBASE-26841.
---------------------------------
    Resolution: Duplicate

We've already moved to log4j2.

> Replace log4j with reload4j for hbase-connector
> -----------------------------------------------
>
>                 Key: HBASE-26841
>                 URL: https://issues.apache.org/jira/browse/HBASE-26841
>             Project: HBase
>          Issue Type: Task
>          Components: hbase-connectors
>    Affects Versions: 1.0.0
>            Reporter: Tak-Lon (Stephen) Wu
>            Assignee: Tak-Lon (Stephen) Wu
>            Priority: Major
>             Fix For: 1.1.0
>
>
> As a result of the [discussion thread of replacing log4j with reload4j|https://lists.apache.org/thread/kfmjg6zmvdjqcwolj0oh634nzv42y806] and HBASE-26691, we have replaced log4j with reload4j in branch-2. 
> Where hbase-connector as a part of the community, this JIRA propose to align with the active hbase release and replace log4j with reload4j before the next release of hbase-connector



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