You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Hyunsik Choi (JIRA)" <ji...@apache.org> on 2009/10/01 13:46:23 UTC
[jira] Updated: (HAMA-196) Design the input/output data types
[ https://issues.apache.org/jira/browse/HAMA-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hyunsik Choi updated HAMA-196:
------------------------------
Component/s: graph
Changed the assigned component.
> 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
>
> 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 RecordReader<VERTEX>.
> 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.