[
https://issues.apache.org/jira/browse/GIRAPH-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Reisman updated GIRAPH-13:
------------------------------
Attachment: GIRAPH-13-3.patch
This is another placeholder, but with a lot of improvements.
- Client and AppMaster are much closer to "real life" but will need a couple
more changes (some of the API's I use have fancy wrapper now apparently, and I
need to do a quick upgrade)
- Munge flag used to stitch us into GiraphRunner with minimal pain. If all goes
well, this will be the only place it is used.
- mvn profile set up and building correctly. Using default of 2.0.2-alpha for
now because I have a local machine set up for that, but will change when the
patch is done. Should be able to config this (among YARN-friendly Hadoops
anyway) with -Dhadoop.version=... at the mvn command line at this point anyway.
> 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
>
>
> 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
