You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@crunch.apache.org by "Josh Wills (JIRA)" <ji...@apache.org> on 2013/07/18 09:26:50 UTC
[jira] [Resolved] (CRUNCH-174) Add support for join3 and cogroup3
[ https://issues.apache.org/jira/browse/CRUNCH-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills resolved CRUNCH-174.
-------------------------------
Resolution: Fixed
Fix Version/s: 0.7.0
Thanks Gabriel, I just committed this to master. Will open a separate JIRA to track the union issue.
I understand where you're coming from in terms of Pig-- it's difficult to use that language for any amount of time and not appreciate how powerful cogroups can be.
> 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
> Fix For: 0.7.0
>
> 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