[
https://issues.apache.org/jira/browse/GIRAPH-111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13173537#comment-13173537
]
Jakob Homan commented on GIRAPH-111:
------------------------------------
bq. I'm not clear on why this is necessary.
I agree. Hadoop's file formats, etc. are designed to be exceedingly forgiving
and flexible as to the underlying storage mechanism. Can you point to where
they're lacking for Mesos' case?
bq. We could also copy out the relevant Hadoop I/O classes (InputFormat,
OutputFormat, etc) into Giraph, rename their packages, and begin reworking them
in an appropriate way to better suit Giraph.
-1. Therein lies madness.
> 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
