Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3392
+1
Merging this...
---
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
Github user lincoln-lil commented on the issue:
https://github.com/apache/flink/pull/3392
@greghogan agree with you make this change in 1.3.
---
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
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3392
This change also effects running in a cluster environment where the UDF
requests multiple iterators but accepts that the same iterator is returned, as
in the modified test.
Since this
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3392
@greghogan You are right, this is a bit of an undefined zone here.
In the distributed runtime, all the `Iterables` can be used only once
(because of once consumable streams behind them).
Github user greghogan commented on the issue:
https://github.com/apache/flink/pull/3392
@lincoln-lil @StephanEwen should this PR wait until 2.0? The modified
example shows a breaking change for valid usage.
---
If your project is set up for it, you can reply to this email and have
Github user lincoln-lil commented on the issue:
https://github.com/apache/flink/pull/3392
Appreciated if someone can merge this pr
---
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
Github user StephanEwen commented on the issue:
https://github.com/apache/flink/pull/3392
Looks correct, +1 to merge this
---
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
