[
https://issues.apache.org/jira/browse/FLINK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698717#comment-14698717
]
ASF GitHub Bot commented on FLINK-2462:
---------------------------------------
Github user StephanEwen commented on a diff in the pull request:
https://github.com/apache/flink/pull/1017#discussion_r37146789
--- Diff:
flink-staging/flink-streaming/flink-streaming-core/src/main/java/org/apache/flink/streaming/runtime/tasks/StreamIterationTail.java
---
@@ -25,65 +25,68 @@
import org.apache.flink.streaming.api.watermark.Watermark;
import org.apache.flink.streaming.runtime.io.BlockingQueueBroker;
import org.apache.flink.streaming.runtime.streamrecord.StreamRecord;
-import org.apache.flink.util.StringUtils;
import org.slf4j.Logger;
import org.slf4j.LoggerFactory;
public class StreamIterationTail<IN> extends OneInputStreamTask<IN, IN> {
- private static final Logger LOG =
LoggerFactory.getLogger(StreamIterationTail.class);
+ private static final Logger LOG =
LoggerFactory.getLogger(StreamIterationHead.class);
--- End diff --
Yep, it is. Good catch!
> Wrong exception reporting in streaming jobs
> -------------------------------------------
>
> Key: FLINK-2462
> URL: https://issues.apache.org/jira/browse/FLINK-2462
> Project: Flink
> Issue Type: Bug
> Components: Streaming
> Affects Versions: 0.10
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Blocker
> Fix For: 0.10
>
>
> When streaming tasks are fail and are canceled, they report a plethora of
> followup exceptions.
> The batch operators have a clear model that makes sure that root causes are
> reported, and followup exceptions are not reported. That makes debugging much
> easier.
> A big part of that is to have a single consistent place that logs exceptions,
> and that has a view of whether the operation is still running, or whether it
> has been canceled.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
