[jira] [Updated] (FLINK-18829) Remove logback-related codepaths and configuration file

["Flink Jira Bot (Jira)" <ji...@apache.org>]

     [ 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 stale-minor starter  (was: auto-deprioritized-major starter)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Minor but is unassigned and neither itself nor its Sub-Tasks have been updated for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is still Minor, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> 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: Minor
>              Labels: auto-deprioritized-major, stale-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)