giraph-dev mailing list archives

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


Avery Ching commented on GIRAPH-564:

I like that.

I would still want the user to have access to the Hadoop context though (in some cases it
can be useful - say if you need it for the API of a Hadoop-based InputFormat underneath),
Maybe we could expose Context though ImmutableClassesGiraphConfigurable rather than the actual
API.  Not sure.

The reason for the Configuration->GiraphConfiguration->ImmutableClassesGiraphConfiguration
is strictly for performance.  

GiraphConfiguration provides users with our Giraph-specific configuration methods.  ImmutableClassesGiraphConfiguration
provides us with the classes set and fast to access and create rather than looking them up.
 I'm open to ideas on how to simplify but still give us the performance of fast class access.
> 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