Github user uce commented on the issue:
https://github.com/apache/flink/pull/2913
> Why is that necessary? Can we not just assume that if the attempt is not
equal to the current execution attempt, then the status is some form of
"disposed".
It's not necessary. It's perfectly fine to do it as you describe. Not
having the `currentExecution` set to the producer execution means that the
producer was restarted (hence cancelled or failed). This only made the handling
in `Task` easier, but it should not dictate this change in the
`ExecutionVertex`. I'll change that to only check the `currentExecution` and
handle it accordingly.
---
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.
---
