Jakob Homan commented on GIRAPH-108:

bq. It seems like it shouldn't be too hard to maintain a few drivers, one for 
M/R, one for YARN, and one for Mesos - most of the daemon code is pretty well 
abstracted and shouldn't take a lot of work to port to the other frameworks.
Yes, this is reasonable, although 
bq. It uses a sort of hack to get around the Map/Reduce input format issue
is probably not going to fly.  I'd rather not introduce anything more hacky 
than is strictly necessary.  I'll try to take a look at this code by the end of 
the week.
> Refactor code to run independently of Map/Reduce
> ------------------------------------------------
>                 Key: GIRAPH-108
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-108
>             Project: Giraph
>          Issue Type: Improvement
>          Components: graph
>            Reporter: Ed Kohlwey
>         Attachments: GIRAPH-108
> It would be nice for Giraph to be refactored such that the code could 
> eventually be run outside of map/reduce. This will allow people to write 
> drivers that can run in the cool new resource manager frameworks like Mesos 
> and YARN, and eventually let the application's code base evolve to be 
> independent of map/reduce.

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: http://www.atlassian.com/software/jira


Reply via email to