You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/04/01 09:52:32 UTC

[GitHub] [flink] zentol commented on issue #11583: [FLINK-16883] Scan FLINK_CONF directory for available log4j configura…

zentol commented on issue #11583: [FLINK-16883] Scan FLINK_CONF directory for available log4j configura…
URL: https://github.com/apache/flink/pull/11583#issuecomment-607151946
 
 
   I wouldn't encourage users to overwrite the log4j properties. Any user who has setup something like that will run into issue in 1.11 with the switch to log4j2 and renaming of the property.
   
   A user wanting to use an xml file instead of properties shouldn't have to use an entirely separate way of configuring log4j.
   I find it a lot more convenient and consistent if users could just drop their log4j configuration into conf and have Flink handle the rest. If that requires a bit of magic, well then so be it.
   
   Note that we can of course still switch the order of the jvm parameters, effectively being an orthogonal issue.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services