I think the discuss thread is wise here. The logging API is effectively part of our public API (in terms of our compatibility guarantees), so it's worth noting.
With the service selection mechanism, will this introduce any troubles for us if we're shading the implementation jar? Maybe there's no reason that we would want to... Nice one Istvan. Thanks, Nick On Thu, Dec 11, 2025 at 10:08 AM Istvan Toth <[email protected]> wrote: > Hi! > > I think that it's time to upgrade to slf4j 2.x in HBase. (3.0+, but > possibly 2.7 as well) > SLF4j 1 is no longer developed, and SLF4j 2 has some nice new features like > the fluent API which makes logging more efficient. > > The only major change that I think may affect us is that the logging > backend is now selected via the services mechanism, instead of searching > the classpath for implementations, and is explicitly configurable. > > I was hesitant to open this thread as the code change is trivial, but log4j > is such a fundamental library that I decided to go for a wider discussion. > > https://issues.apache.org/jira/browse/HBASE-29769 > > best regards > Istvan >
