[
https://issues.apache.org/jira/browse/FLINK-4845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15615458#comment-15615458
]
ASF GitHub Bot commented on FLINK-4845:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/2722
[FLINK-4845] [runtime-web] Fix Job Exception page
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 4845_exception
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2722.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2722
----
commit 5d6e7a9848e3ae08d7df478e6e2075291eda7d01
Author: zentol <[email protected]>
Date: 2016-10-28T13:44:19Z
[FLINK-4845] [runtime-web] Fix Job Exception page
----
> Fix Job Exceptions page
> -----------------------
>
> Key: FLINK-4845
> URL: https://issues.apache.org/jira/browse/FLINK-4845
> Project: Flink
> Issue Type: Bug
> Components: Webfrontend
> Affects Versions: 1.2.0
> Reporter: Chesnay Schepler
> Assignee: Chesnay Schepler
> Fix For: 1.2.0
>
>
> The job exceptions page in the WebFrontend is currently broken, displaying
> (null) for every task even if no exception has occurred.
> The JobExceptionsHandlers checks whether an exception has occurred, and thus
> displayed, by checking whether the rootException is null. This worked until
> recently since we worked directly on Throwables, this was jhowever changed to
> stringified version of the exceptions. This had the side-effect that the
> exception is now never null, but "(null)", leading the handler to believe
> that an exception has occurred.
> The checks should be changed to {code}!exception.equals("(null)"){code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
