[GitHub] flink issue #2508: [FLINK-2662] [dataSet] Translate union with multiple outp...

2016-09-20 Thread fhueske
Github user fhueske commented on the issue: https://github.com/apache/flink/pull/2508 Thanks, merging then --- 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,

[GitHub] flink issue #2508: [FLINK-2662] [dataSet] Translate union with multiple outp...

2016-09-19 Thread StephanEwen
Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2508 I think you are right. +1 to merge then --- 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] flink issue #2508: [FLINK-2662] [dataSet] Translate union with multiple outp...

2016-09-19 Thread fhueske
Github user fhueske commented on the issue: https://github.com/apache/flink/pull/2508 Adding a NoOp would prevent the unions from being merged, but the output of the NoOp would still need to be replicated because it needs to be served to two different operators. if you have

[GitHub] flink issue #2508: [FLINK-2662] [dataSet] Translate union with multiple outp...

2016-09-19 Thread StephanEwen
Github user StephanEwen commented on the issue: https://github.com/apache/flink/pull/2508 Another possibility would be to simply add a `NoOp` operator behind a union with multiple outputs with different partitioning schemes. That prevents the unions from being merged. Would