Hi,

I've read some docs
(https://help.aliyun.com/document_detail/182011.html) stating Flink
optimization technique using:

- partitionedJoin = 'true'
- cache = 'ALL'
- blink.partialAgg.enabled=true

However I could not find any official doc references. Are these
supported at all?

Also "partitionedJoin" seemed to have the effect of shuffling input by
joining key so they can fit into memory. I read this
(https://flink.apache.org/news/2015/03/13/peeking-into-Apache-Flinks-Engine-Room.html)
and believes this is already a default behavior of Flink.

Is this optimization not needed even for huge input tables?

Thanks,
Dai

Reply via email to