[
https://issues.apache.org/jira/browse/CRUNCH-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh Wills updated CRUNCH-174:
------------------------------
Attachment: CRUNCH-174.patch
So I ended up working on this one tonight at the behest of a customer, and it
turned out to be not such a good starter patch after all. :)
I added support for cogroups on 3, 4, or N input PTables, and I added some
static inner classes to Tuple3 and Tuple4 that make working with the otherwise
super long Tuple3<Collection<V1>, Collection<V2>, Collection<V3> the much nicer
Tuple3.Collect<V1, V2, V3> (and similarly for Tuple4).
> Add support for join3 and cogroup3
> ----------------------------------
>
> Key: CRUNCH-174
> URL: https://issues.apache.org/jira/browse/CRUNCH-174
> Project: Crunch
> Issue Type: Bug
> Components: Core, MapReduce Patterns
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-174.patch
>
>
> This seemed like a nice starter JIRA: it would be great to have the three
> (and even four!) argument analogues of Join.join() and Cogroup.cogroup(),
> something like:
> PTable<K, Tuple3<V1, V2, V3>> j = Join.join(PTable<K, V1> a, PTable<K, V2> b,
> PTable<K, V3> c);
> ... and similar for co-groups.
--
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
