Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
-
None
Description
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!
Attachments
Attachments
Issue Links
- blocks
-
GIRAPH-285 Release Giraph-1.0
- Resolved