[FLINK-16883] No support for log4j2 configuration formats besides properties

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.11.0
• Component/s: Command Line Client
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned pull-request-available
• Assignee: Unassigned
• Reporter: Fabian Paul
• Created: 31/Mar/20 09:22
• Updated: 29/Mar/22 06:53

Description

If `flink.console.sh` is used to start a Flink cluster the env java opts precede the log settings.  (link)

This way the log settings `log4.configurationFile` will always overwrite previous keys. Since the `log4j.configurationFile` is set to `log4j.properties`, it is not possible to leverage other formats than properties for the configuration.

 

My proposal would be to switch the order of the configurations that the log settings precede the env java opts. Users could then overwrite the default file with their configurations.

 

Issue Links

• duplicates: FLINK-26896 Logging - Support yaml/xml/json format in Log4j2
• is duplicated by: FLINK-21313 Support more log4j2's configuration syntax
• links to: GitHub Pull Request #11583