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

Posted to commits@beam.apache.org by "Aviem Zur (JIRA)" <ji...@apache.org> on 2017/03/20 14:10:41 UTC

[jira] [Assigned] (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 ]

Aviem Zur reassigned BEAM-1757:
-------------------------------

    Assignee: Aviem Zur

> 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: sdk-java-extensions
>            Reporter: Ismaël Mejía
>            Assignee: Aviem Zur
>            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.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)