hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HAMA-196) Design the input/output data types
Date Tue, 06 Oct 2009 02:59:31 GMT

    [ https://issues.apache.org/jira/browse/HAMA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12762487#action_12762487

Edward J. Yoon commented on HAMA-196:

Trunk still use the hadoop/hbase 0.19.x.

> Design the input/output data types
> ----------------------------------
>                 Key: HAMA-196
>                 URL: https://issues.apache.org/jira/browse/HAMA-196
>             Project: Hama
>          Issue Type: New Feature
>          Components: graph
>            Reporter: Hyunsik Choi
>            Assignee: Hyunsik Choi
>         Attachments: HAMA-196.patch
> Like MapReduce, Angrapa also need input/output data types like key/value pairs of MapReduce.
In Angrapa, programs will handle all of data as vertices, each of which has a key and an adjacent
list. Thus, I think it would be good that a key is an array of bytes (i.e., byte [] ) and
an adjacent list is keys. 
> In addition, most of graph algorithms focus on graph features and labels of either vertices
or edges. They may not need keys. Therefore, RecordReader would need only VERTEX; that is
> What do you think about?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message