Github user fhueske commented on the pull request:
https://github.com/apache/flink/pull/1553#issuecomment-183230276
@ramkrish86, no worries :-)
I guess the issue description lacked a bit of detail. Flink's optimizer
checks, if the partitioning produced by the explicit partitioning operator
(hash, range, custom) can be reused for the Reduce. If not, the data is
partitioned again and this time the combiner can be applied, since it is the
regular.
Thanks for working on 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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
