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/10/10 08:26:45 UTC
[jira] [Updated] (CRUNCH-278) Improvements to MapsideJoin code
[ https://issues.apache.org/jira/browse/CRUNCH-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Josh Wills updated CRUNCH-278:
------------------------------
Attachment: CRUNCH-278.patch
[~mkwhitacre] and [~gabriel.reid] I'd be obliged if you guys could take a look at this first cut. I'd like to generalize it somewhat so that you could include DoFns inside of the ReadableSourceBundle<T> instances that could be used for filtering/transforming the map-side inputs.
I'm also not locked into the names or API structure here-- if there's something you guys like better, please let me know.
> Improvements to MapsideJoin code
> --------------------------------
>
> Key: CRUNCH-278
> URL: https://issues.apache.org/jira/browse/CRUNCH-278
> Project: Crunch
> Issue Type: Bug
> Components: Core, MapReduce Patterns
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: CRUNCH-278.patch
>
>
> The fact that we have special-case code in the MapsideJoinStrategy for the in-memory and MR-based Pipeline instances has always bugged me, so I set out to eliminate the distinction between the two impls by creating a new interface, ReadableSourceBundle<T>, that encapsulates the MR and in-memory specific logic for doing mapside joins in order to remove the special-case code in MapsideJoinStrategy and hopefully make other implementations that use our mapside-join patterns much easier to test.
--
This message was sent by Atlassian JIRA
(v6.1#6144)