You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hama.apache.org by "Thomas Jungblut (JIRA)" <ji...@apache.org> on 2012/09/11 13:01:08 UTC
[jira] [Updated] (HAMA-597) Split a GraphJobRunner into multiple
classes
[ https://issues.apache.org/jira/browse/HAMA-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Jungblut updated HAMA-597:
---------------------------------
Attachment: HAMA-597.patch
Deleted the base again, added a aggregation runner.
Still the load vertices method needs to be cleansed. But what do you think about this refactoring? Is this more readable in your opinion?
> 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: Edward J. Yoon
> Fix For: 0.6.0
>
> Attachments: HAMA-597.patch
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira