You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Joydeep Sen Sarma (JIRA)" <ji...@apache.org> on 2008/03/02 07:24:50 UTC
[jira] Commented: (HADOOP-2429) The lowest level map-reduce APIs
should be byte oriented
[ https://issues.apache.org/jira/browse/HADOOP-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574192#action_12574192 ]
Joydeep Sen Sarma commented on HADOOP-2429:
-------------------------------------------
+1
it seems that we should be able to implement a default byte ordered sort right away and offer that as an option (perhaps via a conf option or something). We could write an optimized C/JNI implementation (if we could parse the sequencefiles that is!). Would try to give the Java one a spin (the C one sounds hairy with compression).
> The lowest level map-reduce APIs should be byte oriented
> --------------------------------------------------------
>
> Key: HADOOP-2429
> URL: https://issues.apache.org/jira/browse/HADOOP-2429
> Project: Hadoop Core
> Issue Type: Improvement
> Components: mapred
> 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.