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/05 15:55:49 UTC

[GitHub] [flink] zentol commented on issue #11634: [FLINK-16984][tests] Consolidate Log4j2-test.properties

zentol commented on issue #11634: [FLINK-16984][tests] Consolidate Log4j2-test.properties
URL: https://github.com/apache/flink/pull/11634#issuecomment-609438563
 
 
   > some modules seem to have some module specifics encoded in their logging config (I propose the keep the files for those modules)
   
   I would only have special configs in leaf modules. For modules that are depended on you will usually want these logging configs to be propagated. Like for `flink-runtime`. I can't think of a good reason to not use the same logging in `flink-tests`.
   
   I'm fine with keeping them in kafka and yarn-tests since they disable quite a lot (all of hadoop/zookeeper).
   
   > we need to make sure all the developers understand the new mechanism (I guess we should at least send a notice to the dev@ list?)
   
   yes, that was my plan.

----------------------------------------------------------------
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