You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2014/11/17 17:10:36 UTC

[jira] [Resolved] (FLINK-1244) setCombinable() clunky to use

     [ https://issues.apache.org/jira/browse/FLINK-1244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-1244.
---------------------------------
       Resolution: Fixed
    Fix Version/s: 0.8-incubating

Fixed in a296f404ee757f086596f12ea9762d7aaed457ff

Thank you for the patch!

> setCombinable() clunky to use
> -----------------------------
>
>                 Key: FLINK-1244
>                 URL: https://issues.apache.org/jira/browse/FLINK-1244
>             Project: Flink
>          Issue Type: Wish
>          Components: Java API
>    Affects Versions: 0.7.0-incubating
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Trivial
>              Labels: starter
>             Fix For: 0.8-incubating
>
>
> Setting the combinable property for a GroupReduce manually is a bit clunky, since setCombinable() doesn't return the operator.
> A wordcount would look like this:
> {code:java}
> GroupReduceOperator output = source
> 	.map...
> 	.groupBy(1)
> 	.reduceGroup...;
> output.setCombinable(true);
> output.print();
> {code}
> whereas this would be more convenient
> {code:java}
> source
> 	.map...
> 	.groupBy(1)
> 	.reduceGroup...
> 	.setCombinale(true)
> 	.print();
> {code}
> is there a reason for it not returning the operator?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)