[
https://issues.apache.org/jira/browse/MAPREDUCE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830230#action_12830230
]
Doug Cutting commented on MAPREDUCE-326:
----------------------------------------
> it might make more sense to invest in moving the MR framework into "user
> space" rather than replumbing the current implementation to be binary first.
I agree that the two are separate, but I don't see that they cannot be pursued
in parallel. As an Apache project, we pursue directions where there are
volunteers. So, if we agree that this is a long-term desirable direction, and
it can be done without breaking the existing API or significantly harming
performance, we ought not stop an interested party from pursuing it, no?
> The lowest level map-reduce APIs should be byte oriented
> --------------------------------------------------------
>
> Key: MAPREDUCE-326
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-326
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: eric baldeschwieler
>
> As discussed here:
> https://issues.apache.org/jira/browse/HADOOP-1986#action_12551237
> The templates, serializers and other complexities that allow map-reduce to
> use arbitrary types complicate the design and lead to lots of object creates
> and other overhead that a byte oriented design would not suffer. I believe
> the lowest level implementation of hadoop map-reduce should have byte string
> oriented APIs (for keys and values). This API would be more performant,
> simpler and more easily cross language.
> The existing API could be maintained as a thin layer on top of the leaner API.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
