[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13582418#comment-13582418
]
Eli Reisman commented on GIRAPH-13:
-----------------------------------
GraphTaskManager is probably in the o.a.g.graph package and is the
encapsulation of all the BSP stuff that used to happen directly in GraphMapper.
So its not part of the patch. Whats nice about faking out the Mapper#Context
this way, as you said, is it allows us to do fine grained JIRAs to build on
this, and makes this a single, discrete, simple patch for enabling YARN and
nothign else. Let me clean it up and make sure it works (might need to populate
the MapContextImpl I create in GiraphYarnTask with a few more goodies, etc.)
but I'm feeling good about this approach. Will post another patch soon.
> Port Giraph to YARN
> -------------------
>
> Key: GIRAPH-13
> URL: https://issues.apache.org/jira/browse/GIRAPH-13
> Project: Giraph
> Issue Type: New Feature
> Reporter: Jakob Homan
> Assignee: Eli Reisman
> Attachments: GIRAPH-13-1.patch, GIRAPH-13-2.patch, GIRAPH-13-3.patch,
> GIRAPH-13-4.patch
>
>
> Now that YARN (aka MR2 aka MAPREDUCE-279) has been merged into the Hadoop
> trunk, we should think about what it would take to separate out the graph
> processing bits of Giraph from the MR1-specific code so as to take advantage
> of the less-MR centric aspects of YARN, while still supporting both over the
> medium term.
--
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
