Return-Path: 
 <issues-return-24781-apmail-flink-issues-archive=flink.apache.org@flink.apache.org>
X-Original-To: apmail-flink-issues-archive@minotaur.apache.org
Delivered-To: apmail-flink-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D286F180C6
	for <apmail-flink-issues-archive@minotaur.apache.org>;
 Mon, 17 Aug 2015 08:32:45 +0000 (UTC)
Received: (qmail 30896 invoked by uid 500); 17 Aug 2015 08:32:45 -0000
Delivered-To: apmail-flink-issues-archive@flink.apache.org
Received: (qmail 30845 invoked by uid 500); 17 Aug 2015 08:32:45 -0000
Mailing-List: contact issues-help@flink.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@flink.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@flink.apache.org>
List-Post: <mailto:issues@flink.apache.org>
List-Id: <issues.flink.apache.org>
Reply-To: dev@flink.apache.org
Delivered-To: mailing list issues@flink.apache.org
Received: (qmail 30835 invoked by uid 99); 17 Aug 2015 08:32:45 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Aug 2015 08:32:45 +0000
Date: Mon, 17 Aug 2015 08:32:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: issues@flink.apache.org
Message-ID: <JIRA.12850969.1438528379000.81314.1439800365660@Atlassian.JIRA>
In-Reply-To: <JIRA.12850969.1438528379000@Atlassian.JIRA>
References: <JIRA.12850969.1438528379000@Atlassian.JIRA>
 <JIRA.12850969.1438528379731@arcas>
Subject: [jira] [Commented] (FLINK-2462) Wrong exception reporting in
 streaming jobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

ASF GitHub Bot commented on FLINK-2462:
---------------------------------------

Github user aljoscha commented on a diff in the pull request:

    https://github.com/apache/flink/pull/1017#discussion_r37167205
  
    --- Diff: flink-staging/flink-streaming/flink-streaming-core/src/main/java/org/apache/flink/streaming/api/operators/Output.java ---
    @@ -33,9 +33,8 @@
     	 * Emits a {@link Watermark} from an operator. This watermark is broadcast to all downstream
     	 * operators.
     	 *
    -	 * <p>
    -	 * A watermark specifies that no element with a timestamp older or equal to the watermark
    -	 * timestamp will be emitted in the future.
    +	 * <p>A watermark specifies that no element with a timestamp older or equal to the watermark
    --- End diff --
    
    Why did you change this? The oracle Javadoc literature (http://www.oracle.com/technetwork/articles/java/index-137868.html) and style guides (http://blog.joda.org/2012/11/javadoc-coding-standards.html) have it like it was. Javadoc is not HTML so tags like <li> <p> and so on are not closed.


> 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)