[
https://issues.apache.org/jira/browse/HAMA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13412812#comment-13412812
]
Thomas Jungblut commented on HAMA-597:
--------------------------------------
There is the Job class concept which MapReduce already uses.
Hama has quite the same interfaces to submit the jobs like MapReduce has
(job.submit, job.waitForCompletion). And as you may know, Giraph runs on top of
MapReduce so basically it is the same.
What you are looking for is something that creates a common interface to start
these jobs. That is not what the GraphJobRunner does, it is a bridge between
the native BSP model and the higher level vertex abstraction in the Pregel
paper.
The handling of job start and submission is handled by the GraphJob. And I do
suggest you to not create a constant interface throughout various projects
since there are too many options that diverge.
> 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
