[
https://issues.apache.org/jira/browse/FLINK-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15945096#comment-15945096
]
ASF GitHub Bot commented on FLINK-6043:
---------------------------------------
Github user tillrohrmann commented on the issue:
https://github.com/apache/flink/pull/3583
It's not per se horrible to pass on the timestamp. In my opinion it's just
a good idea trying to keep the interface as lean as possible to avoid making
mistakes. If we say that we want to display a consistent timestamp, then I
think we have to pass it to the `ExecutionGraph` as you've done it.
> Display time when exceptions/root cause of failure happened
> -----------------------------------------------------------
>
> Key: FLINK-6043
> URL: https://issues.apache.org/jira/browse/FLINK-6043
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Assignee: Chesnay Schepler
> Priority: Minor
>
> In order to better understand the behaviour of Flink jobs, it would be nice
> to add timestamp information to exception causing the job to restart or to
> fail. This information could then be displayed in the web UI making it easier
> for the user to understand what happened when.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
