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