[
https://issues.apache.org/jira/browse/MAPREDUCE-326?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12831537#action_12831537
]
Milind Bhandarkar commented on MAPREDUCE-326:
---------------------------------------------
> Back to a low-level binary API: the proposal here isn't to deprecate any
> higher level APIs, but rather to add a new lower-level API that we can
> implement both the current APIs and new APIs atop. This should in fact help
> us to preserve high-level API compatibility longer, since the mapreduce
> kernel will be independent of the high-level API.
+1 !!
I have always thought of hadoop MR APIs as assembly language, and gradually no
one will use it directly. The low-level APIs will be great for Pig, Hive, HBase
and other high-level languages to translate to, without making compromises for
efficiency.
> 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.
