crunch-dev mailing list archives

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

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

Gabriel Reid commented on CRUNCH-174:
-------------------------------------

Yep, exactly -- I just realized the same thing (or at least that this would only work if only
a single datatype is used).

The union PType sounds like a good plan, but it also sounds like a separate JIRA. Definitely
not worth blocking this one before we have a union type.

With that in mind, +1 for the patch as-is.
                
> 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