flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Till Rohrmann (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-1355) Inconsistent Logging/Printing for Examples
Date Tue, 06 Jan 2015 09:36:34 GMT

    [ https://issues.apache.org/jira/browse/FLINK-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14265897#comment-14265897

Till Rohrmann commented on FLINK-1355:

The reason why one sees the warning about the logging backend is because there is no log4j.properties/logback.xml
file in ones classpath or one has not specified a properties file. Technically, then the logging
is disabled. To get rid off these warnings one needs to provide a log4j.properties file. The
problem is that we don't want to ship a predefined logging file with the binaries, because
it could later interfere with a user provided file. Therefore, there is no configuration file
in the resources folder, except for log4j-test.properties which does not conform to the naming
conventions and, thus, is fine.

If the user runs an example from the command line, then he sees the logging output (INFO level
if he uses the provided log4j.properties file) and the sysout currently. By disabling the
sysout by default, he would only see the results of the example if run from within the IDE
because of the missing logging file (if not specifically set). If 0.8 is shipped like that,
then we probably should conform to that behavior. I'm just wondering what happens if the user
has a program with a file output. Then he would see nothing as output from the IDE. Is that
the desired behavior?

> Inconsistent Logging/Printing for Examples
> ------------------------------------------
>                 Key: FLINK-1355
>                 URL: https://issues.apache.org/jira/browse/FLINK-1355
>             Project: Flink
>          Issue Type: Bug
>            Reporter: Stephan Ewen
>            Assignee: Till Rohrmann
>            Priority: Minor
> When running examples from the IDE, I see a warning that no logging backend is configured,
and I see System.out printing from the client.
> in 0.8, the client's sysout printing is disabled in the local mode.
> We can change it to by default disable logging and enable the client sysout output, or
vice versa, but I think we should not have both.

This message was sent by Atlassian JIRA

View raw message