crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-282) Add a cap on the number of reducers per job
Date Thu, 17 Oct 2013 06:38:41 GMT

    [ https://issues.apache.org/jira/browse/CRUNCH-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13797661#comment-13797661
] 

Gabriel Reid commented on CRUNCH-282:
-------------------------------------

+1, super useful. It would be a good idea to squash the two commits in the most recent patch
into a single commit just so it's more clear in the commit history.

> Add a cap on the number of reducers per job
> -------------------------------------------
>
>                 Key: CRUNCH-282
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-282
>             Project: Crunch
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 0.7.0
>            Reporter: Josh Wills
>            Assignee: Josh Wills
>         Attachments: CRUNCH-282.patch, CRUNCH-282.patch
>
>
> Like Pig, Crunch should have a parameter that controls the maximum number of reducers
to use for a given job when Crunch sets the number by estimating the size of the input data
set. I'm thinking "crunch.max.reducers" with a default of 500.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message