giraph-dev mailing list archives

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


Alessandro Presta commented on GIRAPH-564:

Here's an alternative idea: make the base input formats implement ImmutableClassesGiraphConfigurable,
and provide methods like createVertex(), createEdge() as part of their API. This way, the
user doesn't have to deal with the configuration, EdgeFactory etc, and also the nuances of
instantiation vs initialization.
We discussed it here:

Another related improvement would be simplifying the configuration hierarchy: right now we
have Hadoop's Configuration, from which we create a GiraphConfiguration, from which we create
an ImmutableClassesGiraphConfiguration.
It would be good to only expose a GiraphConfiguration to the user, which would extend Hadoop's
Configuration (giving access to all options), but also have the Giraph-specific methods and
cached classes. Do you think this is doable?
> 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