[
https://issues.apache.org/jira/browse/MAPREDUCE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12829722#action_12829722
]
Todd Lipcon commented on MAPREDUCE-326:
---------------------------------------
bq. This is a possible long-term direction, not an immediate plan
Completely agree. I'm just trying to present some wild ideas to spur discussion
in different directions.
bq. Do folks see another way to achieve real language independence, where both
mapreduce clients and servers may be implemented in other languages
I think we need to distinguish the user/library facing API from the internal
communication mechanisms. Task language independence has some commonality with
service language independence, but I think they also have a lot of different
bits. But, to answer your question, yes, I think this should be a long term
goal.
> 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.
