giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nitay Joffe (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-564) Input formats should provide GiraphContext
Date Fri, 15 Mar 2013 17:24:12 GMT


Nitay Joffe commented on GIRAPH-564:

Why would you want a GiraphConfiguration if you have an ImmutableClassesGiraphConfiguration?
In that case might as well just rename the latter to GiraphConfiguration and use it everywhere.
Also why not just have a per-thread ImmutableClassesGiraphConfiguration that is globally accessible or
something like that?
> Input formats should provide GiraphContext
> ------------------------------------------
>                 Key: GIRAPH-564
>                 URL:
>             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:

View raw message