incubator-giraph-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Avery Ching (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GIRAPH-111) Refactor I/O to be independent of Map/Reduce
Date Tue, 20 Dec 2011 21:23:30 GMT

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

Avery Ching commented on GIRAPH-111:
------------------------------------

I'm not clear on why this is necessary.  Couldn't we simply call the I/O methods as Hadoop
would when we're not using Hadoop?  Am I missing something?
                
> 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

        

Mime
View raw message