You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2019/01/10 14:09:01 UTC

[jira] [Closed] (FLINK-3144) [storm] LocalCluster prints nothing without a configured logger

     [ https://issues.apache.org/jira/browse/FLINK-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-3144.
-----------------------------------
    Resolution: Won't Fix

The storm-compatibility layer will be removed in FLINK-10509.

> [storm] LocalCluster prints nothing without a configured logger
> ---------------------------------------------------------------
>
>                 Key: FLINK-3144
>                 URL: https://issues.apache.org/jira/browse/FLINK-3144
>             Project: Flink
>          Issue Type: Bug
>          Components: Storm Compatibility
>    Affects Versions: 0.10.0, 0.10.1
>            Reporter: Maximilian Michels
>            Assignee: Maximilian Michels
>            Priority: Major
>
> When no loggers have been configured, i.e. log4j.properties is not present in the classpath, Storm local cluster executions print nothing. This may be counter-intuitive for the user.
> The reason for this behavior is that the Storm job is submitted detached to make it execute non-blocking. Instead, we should submit it non-detached in a separate thread. We can then enable printing to sysout in addition to logging like regular Flink jobs do it as well.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)