Github user sachingoel0101 commented on the pull request:
https://github.com/apache/flink/pull/1214#issuecomment-145059638
It doesn't really make sense to call `print` or `collect` in detached mode.
Even if the result is printed on JobManager, client cannot access it anyway
[short of going through the std out logs of JM].
Also, right now, the stack trace for this failure is uninformative.
I propose to explicitly disallow functions which access Accumulator results
in detached mode *viz* `count`, `collect` and `print`. What do you think?
We can provide a hint that a sink should be used instead in the exception
message.
---
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.
---