hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mirko Kaempf (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-597) Split a GraphJobRunner into multiple classes
Date Thu, 12 Jul 2012 13:58:34 GMT

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

Mirko Kaempf commented on HAMA-597:
-----------------------------------

To your question "But what is the reason to make it comparable to giraph?"

I started a review on availlable graph processing tools, so I found this: 
(http://blog.acaro.org/entry/google-pregel-the-rise-of-the-clones)

"So, to summarize, what Hame, GoldenOrb and Giraph have in common is: Java platform, Apache
License (and incubation), BSP computation. What they differ for: Hama offers BSP primitives
not graph processing API (so it sits at a lower level)..."

In a separate project, it is called "hadoop distributed graph space" (HDGS) a Metadata store
for graph processing (like Hive warehouse) and a generic workflow framework (compatible to
Oozie) is under construction which is running on top of HDFS and HBase in a hadoop cluster.

I would like to see a common way to start these jobs based on HAMA and Giraph or simple MapReduce
(for example for preprocessing graph data sets by analysing time series data in a comparable
way, so it would be easy to have applications on a higher abstraction level which build workflows
by combining different tasks using different computational concepts in one single Hadoop cluster.

 
                
> Split a GraphJobRunner into multiple classes
> --------------------------------------------
>
>                 Key: HAMA-597
>                 URL: https://issues.apache.org/jira/browse/HAMA-597
>             Project: Hama
>          Issue Type: Improvement
>          Components: graph
>    Affects Versions: 0.5.0
>            Reporter: Edward J. Yoon
>            Assignee: Mirko Kaempf
>             Fix For: 0.6.0
>
>
> Really not readable and maintainable.
> Break up pieces of functionality into their own classes.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message