lizer [1]. The partition operator adds
another task which instantiates another thread. Consequently,
coGroup(b).where(...).equalTo(...).withPartitioner(...) should be slightly
more efficient.
[1] https://flink.apache.org/visualizer/
Cheers,
Till
On Sun, Dec 2, 2018 at 1:35 PM Giannis Evagorou
Hi all,
I have a question regarding partitioning.
Does calling the withPartitioner() method on a coGroup operation has the same
effect as performing partitionCustom on both datasets beforehand?
i.e.
Is
1. a.coGroup(b).where(…).equalTo(…).withPartitioner(…).with(…)
equivalent to:
1. Da
