incubator-crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gabriel Reid (JIRA)" <>
Subject [jira] [Commented] (CRUNCH-51) PCollection#sort relies on using a single reducer for total order sorting
Date Mon, 17 Sep 2012 10:05:07 GMT


Gabriel Reid commented on CRUNCH-51:

I was just doing some general testing with this, and ran into a couple of issues:

- it seems that this patch doesn't work with descending (i.e. reverse-order) sorting. When
I tried reverse-order sorting strings, I got an IOException with "Split points are out of
- sorting reflection-based Avro or generic records in Avro doesn't seem to work -- in both
cases I got a message of "Number of keys to write in partion file:0" and then a materialize
crashes due to the file to be materialized not existing

Apart from these issues, I think it's looking pretty good. The Avro reflection sorting issue
seems pretty minor to me (i.e. not a very common use case), but this is something that does
work right now with the single-reducer solution.
> PCollection#sort relies on using a single reducer for total order sorting
> -------------------------------------------------------------------------
>                 Key: CRUNCH-51
>                 URL:
>             Project: Crunch
>          Issue Type: Improvement
>    Affects Versions: 0.3.0
>            Reporter: Gabriel Reid
>         Attachments: 0001-CRUNCH-51-Total-Order-Sort.patch, CRUNCH-51.patch
> The total-order sorting provided by the Sort class (and therefore PCollection#sort) relies
on using a single reducer in order to provide total-order sorting. This is very inefficient
for large datasets, and should be replaced with a total order partitioner instead.
> For more information, see CRUNCH-23 (and possibly also MAPREDUCE-4574).

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:

View raw message