giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alessandro Presta (JIRA)" <>
Subject [jira] [Updated] (GIRAPH-595) should take GiraphConfiguration, not GiraphClasses
Date Fri, 12 Apr 2013 21:26:20 GMT


Alessandro Presta updated GIRAPH-595:

    Attachment: GIRAPH-595.patch
> should take GiraphConfiguration, not GiraphClasses
> -----------------------------------------------------------------------------
>                 Key: GIRAPH-595
>                 URL:
>             Project: Giraph
>          Issue Type: Bug
>            Reporter: Alessandro Presta
>            Assignee: Nitay Joffe
>         Attachments: GIRAPH-595.patch, GIRAPH-595.patch
> 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:

View raw message