[
https://issues.apache.org/jira/browse/CRUNCH-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697577#comment-13697577
]
Gabriel Reid commented on CRUNCH-231:
-------------------------------------
Yeah, I can definitely follow Dave's reasoning here -- but I'm also definitely
+1 on adding this functionality (haven't had a chance to take a look at the
patch yet though).
I see this as being potentially really useful for integrating with something
like Mahout, where lots of interesting functionality that has been implemented
directly in Mapper and Reducer classes. This shouldn't be the primary way of
working with Crunch (obviously), but I really think it's a nice thing to have.
> Support legacy Mappers and Reducers in Crunch pipelines
> -------------------------------------------------------
>
> Key: CRUNCH-231
> URL: https://issues.apache.org/jira/browse/CRUNCH-231
> Project: Crunch
> Issue Type: Improvement
> Components: Core
> Reporter: Josh Wills
> Assignee: Josh Wills
> Attachments: mapred.patch
>
>
> I've had a few requests for Crunch to support existing Mappers and Reducers
> using the underlying Java APIs as part of regular pipelines, so that users
> could evolve existing MapReduce jobs into Crunch pipelines gradually, instead
> of being forced to rewrite everything all at once in order to map it onto
> Crunch's model.
--
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