flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Luke Hutchison (JIRA)" <j...@apache.org>
Subject [jira] [Created] (FLINK-6028) Unnamed operations in main method logged as "main(null:-1)"
Date Mon, 13 Mar 2017 08:53:04 GMT
Luke Hutchison created FLINK-6028:
-------------------------------------

             Summary: Unnamed operations in main method logged as "main(null:-1)"
                 Key: FLINK-6028
                 URL: https://issues.apache.org/jira/browse/FLINK-6028
             Project: Flink
          Issue Type: Bug
          Components: Core
    Affects Versions: 1.2.0
            Reporter: Luke Hutchison
            Priority: Trivial


If in main I have some code like this:

{code}
x.filter(t -> !t.f0.isEmpty())
    .flatMap((t, out) -> out.collect(new Tuple3<>(t.f1, t.f2, t.f3)))
    .writeAsText(filename, WriteMode.OVERWRITE).setParallelism(1);
{code}

In the log, the origin of these unnamed operations shows up as "main(null:-1)":

{noformat}
CHAIN Filter (Filter at main(null:-1)) -> FlatMap (FlatMap at main(null:-1))(2/2) switched
to SCHEDULED 
{noformat}

However, operations inside lambdas seem to correctly provide the class name and line number
in the logs, e.g. "Main.java:217".



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

Mime
View raw message