[
https://issues.apache.org/jira/browse/FLINK-16883?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17191736#comment-17191736
]
Kars de Jong commented on FLINK-16883:
--------------------------------------
Unfortunately the switch to log4j2 broke our current setup, because we had
already switched to it. We however use a .xml file to configure it, which is no
longer possible because we can't override the log4j.configurationFile setting.
The GitHub pull request has been closed because there was no consensus.
> No support for log4j2 configuration formats besides properties
> --------------------------------------------------------------
>
> Key: FLINK-16883
> URL: https://issues.apache.org/jira/browse/FLINK-16883
> Project: Flink
> Issue Type: Improvement
> Components: Command Line Client
> Affects Versions: 1.11.0
> Reporter: Fabian Paul
> Assignee: Fabian Paul
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> If `flink.console.sh` is used to start a Flink cluster the env java opts
> precede the log settings.
> ([link|https://github.com/apache/flink/blob/master/flink-dist/src/main/flink-bin/bin/flink-console.sh#L73])
> 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.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
