FAQ
The lowest level map-reduce APIs should be byte oriented
--------------------------------------------------------

Key: HADOOP-2429
URL: https://issues.apache.org/jira/browse/HADOOP-2429
Project: Hadoop
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.

Search Discussions

  • Runping Qi (JIRA) at Dec 14, 2007 at 8:06 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12551923 ]

    Runping Qi commented on HADOOP-2429:
    ------------------------------------

    +1

    To enforce that, the API should use concrete classes (such as Buffer) instead of interface classes such as ByteWritable.

    One difficult, though, is the implementation of key based comparison and
    sorting. To perform key comparison, the framework may have to
    deserialize them, unless making it mandatory for the application to
    provide a bytes based comparison function.

    The lowest level map-reduce APIs should be byte oriented
    --------------------------------------------------------

    Key: HADOOP-2429
    URL: https://issues.apache.org/jira/browse/HADOOP-2429
    Project: Hadoop
    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.
  • Sameer Paranjpye (JIRA) at Jan 22, 2008 at 11:44 pm
    [ https://issues.apache.org/jira/browse/HADOOP-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

    Sameer Paranjpye updated HADOOP-2429:
    -------------------------------------

    Component/s: mapred
    The lowest level map-reduce APIs should be byte oriented
    --------------------------------------------------------

    Key: HADOOP-2429
    URL: https://issues.apache.org/jira/browse/HADOOP-2429
    Project: Hadoop
    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.

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupcommon-dev @
categorieshadoop
postedDec 14, '07 at 5:04p
activeJan 22, '08 at 11:44p
posts3
users1
websitehadoop.apache.org...
irc#hadoop

1 user in discussion

Sameer Paranjpye (JIRA): 3 posts

People

Translate

site design / logo © 2022 Grokbase