Github user zentol commented on the pull request:
https://github.com/apache/flink/pull/1375#issuecomment-157721238
Always throwing an exception prevents access to the JobExecutionResult when
using collect() or a print().
This discussion on JIRA makes it seem like it does affect a lot of people
though. The current behaviour causes issues, is there any case where a
redundant execute() call will break things?
---
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.
---
