flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3179) Combiner is not injected if Reduce or GroupReduce input is explicitly partitioned
Date Tue, 08 Mar 2016 08:23:41 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15184641#comment-15184641

ASF GitHub Bot commented on FLINK-3179:

Github user fhueske commented on the pull request:

    Hi @ramkrish86, I totally understand that you are disappointed. I'm very sorry to raise
these concerns this late after you put a lot of effort into this PR. I should have noticed
this issue much earlier :-( 
    Touching the optimizer is always a little bit like open heart surgery and must be done
very carefully with the whole picture in mind. I have not completely investigated the possible
side effects yet, but will definitely let you know once I have.
    Would you like to work on a different issue in the meantime?

> Combiner is not injected if Reduce or GroupReduce input is explicitly partitioned
> ---------------------------------------------------------------------------------
>                 Key: FLINK-3179
>                 URL: https://issues.apache.org/jira/browse/FLINK-3179
>             Project: Flink
>          Issue Type: Bug
>          Components: Optimizer
>    Affects Versions: 0.10.1
>            Reporter: Fabian Hueske
>            Assignee: ramkrishna.s.vasudevan
>            Priority: Critical
>             Fix For: 1.0.0, 0.10.2
> The optimizer does not inject a combiner if the input of a Reducer or GroupReducer is
explicitly partitioned as in the following example
> {code}
> DataSet<Tuple2<String,Integer>> words = ...
> DataSet<Tuple2<String,Integer>> counts = words
>   .partitionByHash(0)
>   .groupBy(0)
>   .sum(1);
> {code}
> Explicit partitioning can be useful to enforce partitioning on a subset of keys or to
use a different partitioning method (custom or range partitioning).
> This issue should be fixed by changing the {{instantiate()}} methods of the {{ReduceProperties}}
and {{GroupReduceWithCombineProperties}} classes such that a combine is injected in front
of a {{PartitionPlanNode}} if it is the input of a Reduce or GroupReduce operator. This should
only happen, if the Reducer is the only successor of the Partition operator.

This message was sent by Atlassian JIRA

View raw message