[
https://issues.apache.org/jira/browse/FLINK-16883?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-16883:
-----------------------------------
Labels: auto-unassigned pull-request-available stale-major (was:
auto-unassigned pull-request-available)
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
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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
> Priority: Major
> Labels: auto-unassigned, pull-request-available, stale-major
> 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)
