[ https://issues.apache.org/jira/browse/FLINK-2462?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stephan Ewen resolved FLINK-2462. --------------------------------- Resolution: Fixed Fixed via 92b1e471d4762545637817c74f9396765984b39a > 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)