incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jakob Homan (Commented) (JIRA)" <>
Subject [jira] [Commented] (GIRAPH-111) Refactor I/O to be independent of Map/Reduce
Date Wed, 21 Dec 2011 21:39:31 GMT


Jakob Homan commented on GIRAPH-111:

So this is about counters/reporting (ie, all the stuff that's being proxied by HadoopContext
in GIRAPH-108)? Yeah, that will need to be handled in a more generic way once Giraph is less
MR-centric.  GIRAPH-77 was actually intended to partially work on this by creating a central
places for statistics to be handled (and exposed initially via a webpage) and then hooked
into whatever the proper final destination was for whatever framework we're running on top
of.  I'm afraid I'm still not sure how this brings in {Input|Output}Formats into the mix.
> Refactor I/O to be independent of Map/Reduce
> --------------------------------------------
>                 Key: GIRAPH-111
>                 URL:
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>            Reporter: Ed Kohlwey
> The I/O mechanisms should probably be abstracted entirely from Map/Reduce in order to
support making Giraph an independent framework.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message