[Bug] SLF4J and Logback version compatibility

[michaelkoepf]

Search before asking

• I searched in the issues and found nothing similar.

Fluss version

Fluss currently uses SLF4J version 1.7.36. The docs describe how to use Logback with SLF4J but do not point out that newer Logback version are incompatible with SLF4J 1.x. When using Logback >= 1,3, the application start will fail.

Minimal reproduce step

• Configure Logback >= 1.3 as logging backend
• Starting Fluss will fail with the following error messages

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
SLF4J: Defaulting to no-operation MDCAdapter implementation.
SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.

What doesn't meet your expectations?

Since the SLF4J website has changed and the provided URLs don't really help to troubleshoot the problem, we should add a hint to the doc that users should use Logback <= 1.2.x

Anything else?

No response

Are you willing to submit a PR?

• I'm willing to submit a PR!