crunch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Wills (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CRUNCH-174) Add support for join3 and cogroup3
Date Thu, 18 Jul 2013 07:02:48 GMT

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

Josh Wills commented on CRUNCH-174:
-----------------------------------

I agree with that; the trick as I see it is that we don't have a notion of a PType<Union<A,
B, ...>> at this point. Adding one for Avro is really straightforward; adding one for
Writables is a little bit more interesting (but not that bad). I think we would just need
to agree on what the Union class(es) looked like and where they would live in the package
hierarchy.
                
> 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

Mime
View raw message