[
https://issues.apache.org/jira/browse/FLINK-21190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17273510#comment-17273510
]
Matthias commented on FLINK-21190:
----------------------------------
[~vthinkxie] Your proposal looks good. I'm still wondering how we could hide
the stacktraces, though. We could make the entries of the nested table
collapsible to hide the stacktraces there. But how do we do this for the root
cause's stacktrace?
Two options I can think of are:
1. The root cause is also part of the nested table. We have to mark this one in
some way to enable the user to identify it as the root (different background,
first element in the list).
2. We list the root cause information in the parent entry (like the blue
background entry) and expose the stack trace on top of the nested table
containing other related task failures (w/o the root cause).
> Expose extended exception history through REST handler and adapt UI
> accordingly
> -------------------------------------------------------------------------------
>
> Key: FLINK-21190
> URL: https://issues.apache.org/jira/browse/FLINK-21190
> Project: Flink
> Issue Type: Sub-task
> Reporter: Matthias
> Priority: Major
>
> A first idea of a UI change was proposed by [~vthinkxie] in the parent task:
> !https://issues.apache.org/jira/secure/attachment/13019553/13019553_%E6%88%AA%E5%B1%8F2021-01-28+%E4%B8%8B%E5%8D%884.47.46.png|width=476,height=245!
> The {{JobExceptionsHandler}} response should be extended introducing a new
> (deprecated) field {{otherFailures}}. This way we avoid breaking the API.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
