You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@crunch.apache.org by "Gabriel Reid (JIRA)" <ji...@apache.org> on 2013/01/07 17:24:17 UTC

[jira] [Updated] (CRUNCH-139) PCollection#length doesn't always reduce the count to a single value

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

Gabriel Reid updated CRUNCH-139:
--------------------------------

    Attachment: CRUNCH-139.patch

Simple patch to fix the issue
                
> PCollection#length doesn't always reduce the count to a single value
> --------------------------------------------------------------------
>
>                 Key: CRUNCH-139
>                 URL: https://issues.apache.org/jira/browse/CRUNCH-139
>             Project: Crunch
>          Issue Type: Bug
>            Reporter: Gabriel Reid
>            Assignee: Gabriel Reid
>             Fix For: 0.5.0
>
>         Attachments: CRUNCH-139.patch
>
>
> PCollection#length doesn't explicitly set the number of reducers to 1, which means that the output of the counting mappers can be partitioned. This results only a partial count (i.e. an incorrect value) being returned in the length PObject if the input PCollection spans multiple default reduce partitions.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira