[ https://issues.apache.org/jira/browse/FLINK-18829?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Flink Jira Bot updated FLINK-18829: ----------------------------------- Labels: auto-deprioritized-major auto-deprioritized-minor starter (was: auto-deprioritized-major stale-minor starter) Priority: Not a Priority (was: Minor) This issue was labeled "stale-minor" 7 days ago and has not received any updates so it is being deprioritized. If this ticket is actually Minor, please raise the priority and ask a committer to assign you the issue or revive the public discussion. > Remove logback-related codepaths and configuration file > ------------------------------------------------------- > > Key: FLINK-18829 > URL: https://issues.apache.org/jira/browse/FLINK-18829 > Project: Flink > Issue Type: Technical Debt > Components: Deployment / Scripts, Runtime / Coordination > Reporter: Robert Metzger > Priority: Not a Priority > Labels: auto-deprioritized-major, auto-deprioritized-minor, > starter > > Flink currently (1.12-SNAPSHOT) provides support for two logging backends: > Log4j2 (default) and logback. > The logback support is not really covered by our testing, and there's little > evidence of widespread use. > Users can use a custom logging backend (as long as it's supported by slf4j) > by providing the appropriate configuration files and jars in the classpath of > all Flink services. Therefore, we should remove the logback-related files and > codepaths in Flink and let our users set things up themselves. -- This message was sent by Atlassian Jira (v8.20.1#820001)