You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beam.apache.org by "Luke Cwik (JIRA)" <ji...@apache.org> on 2017/07/05 18:46:00 UTC
[jira] [Updated] (BEAM-1757) Improve log configuration when using
multiple logging frameworks in Pipeline
[ https://issues.apache.org/jira/browse/BEAM-1757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Luke Cwik updated BEAM-1757:
----------------------------
Component/s: beam-model-runner-api
beam-model-fn-api
> Improve log configuration when using multiple logging frameworks in Pipeline
> ----------------------------------------------------------------------------
>
> Key: BEAM-1757
> URL: https://issues.apache.org/jira/browse/BEAM-1757
> Project: Beam
> Issue Type: Improvement
> Components: beam-model-fn-api, beam-model-runner-api, sdk-java-extensions
> Reporter: Ismaël Mejía
> Priority: Minor
>
> We need to improve / document how to configure the different logging frameworks to support the different Beam modules (SDK/Runners/IOs).
> I have seen this reported already in slack, but it also bit me recently when trying to log things with a module whose dependencies only supported java based logging over slf4j (no log4j). I tried to provide the classical log4j.properties but I could not get it to log anything, nothing from the sdk, and logically nothing from the java logging framework.
> [Discussion on dev list|https://lists.apache.org/thread.html/502fc4a0575534ddd5f6abffd0743de8d2ccc7fee078b5922c2e1300@%3Cdev.beam.apache.org%3E]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)