[
https://issues.apache.org/jira/browse/GIRAPH-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13603551#comment-13603551
]
Avery Ching commented on GIRAPH-564:
------------------------------------
Maybe we could split the immutable and mutable parts up into two different
classes. The immutable classes could then we used anywhere for class
instantiation and the user could keep playing with a mutable
GiraphConfiguration.
> Input formats should provide GiraphContext
> ------------------------------------------
>
> Key: GIRAPH-564
> URL: https://issues.apache.org/jira/browse/GIRAPH-564
> Project: Giraph
> Issue Type: Improvement
> Affects Versions: 0.2.0
> Reporter: Avery Ching
>
> Context is a MapReduce Context that input classes have to explicitly create a
> ImmutableGiraphClassesConfiguration from (which is not intuitive). It would
> be better to provide a GiraphContext that would provide a
> ImmutableGiraphClassesConfiguration directly for the user, while still
> providing the user access to the MapReduce Context if really necessary. This
> might also help with the YARN port? Not sure.
--
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
