hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HAMA-597) Split a GraphJobRunner into multiple classes
Date Tue, 11 Sep 2012 06:29:08 GMT

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

Thomas Jungblut commented on HAMA-597:

Do you think that this will lower the complexity? Personally we should extract a single superstep
and refactor it into clean methods. Extracting a base class if we don't have multiple implementations
is just confusing.
> 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
> 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

View raw message