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

Flink Jira Bot updated FLINK-18829:
-----------------------------------
    Labels: stale-major starter  (was: starter)

> Remove logback-related codepaths and configuration file
> -------------------------------------------------------
>
>                 Key: FLINK-18829
>                 URL: https://issues.apache.org/jira/browse/FLINK-18829
>             Project: Flink
>          Issue Type: Task
>          Components: Deployment / Scripts, Runtime / Coordination
>            Reporter: Robert Metzger
>            Priority: Major
>              Labels: stale-major, 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.3.4#803005)

Reply via email to