Github user zentol commented on the issue:
https://github.com/apache/flink/pull/3583
@tillrohrmann I've addressed your comments regarding ErrorInfo being
volatile/fields being final as well as markTimestamp generating and returning
the timestamp.
@StephanEwen @tillrohrmann Regarding the timestamp in notifyStateTransiton
etc. :The webUI displays 2 kind of exceptions: 1) the root exception that is
stored in the ExecutionGraph and 2) a list of task exceptions that are stored
in the Executions. IMO, if the exception stored in an Execution is also the
root exception in the EG then the timestamps should match to be consistent and
not give off the impression that these are unrelated/different. To that end the
Execution has to supply the Exception as well as the timestamp. We could create
the ErrorInfo directly in the Execution and pass that on instead of just the
exception. This would make it move obvious that the TS is related to the
exception i suppose.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
