Github user fhueske commented on the pull request:
https://github.com/apache/incubator-flink/pull/84#issuecomment-50535230
I think throwing a meaningful exception when accessing the iterator a
second time is the more intuitive and user-friendly option. I think it is
easier to get a function right, if an exception explicitly tells you what you
are doing wrong rather than debugging the code and wondering why the stupid
iterator is empty...
+1 to throw an exception when the iterator is requested the second time.
---
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.
---
