You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@giraph.apache.org by "Alessandro Presta (JIRA)" <ji...@apache.org> on 2013/03/27 19:51:16 UTC

[jira] [Created] (GIRAPH-595) InternalVertexRunner.run() should take GiraphConfiguration, not GiraphClasses

Alessandro Presta created GIRAPH-595:
----------------------------------------

             Summary: InternalVertexRunner.run() should take GiraphConfiguration, not GiraphClasses
                 Key: GIRAPH-595
                 URL: https://issues.apache.org/jira/browse/GIRAPH-595
             Project: Giraph
          Issue Type: Bug
            Reporter: Alessandro Presta


The current way GiraphClasses is used is not ideal for two reasons:
1) InternalVertexRunner has to add all those wrapper calls like conf.setXXXClass(classes.getXXXClass()). This is verbose and fragile since it has to be updated every time we add a new type of class.
2) The configuration flow is circular: the user creates a GiraphClasses, which is used to create GiraphConfiguration, which is used to create ImmutableClassesGiraphConfiguration, which creates a new GiraphClasses!

--
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