[ 
https://issues.apache.org/jira/browse/GIRAPH-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13174429#comment-13174429
 ] 

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: https://issues.apache.org/jira/browse/GIRAPH-111
>             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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to