[
https://issues.apache.org/jira/browse/GIRAPH-631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eli Reisman resolved GIRAPH-631.
--------------------------------
Resolution: Fixed
Assignee: Eli Reisman
I think we're good here at this point. Several patches are up for review that
make 2.0.4 and 2.0.5 as well as variable YARN versions + YARN Giraph profile
work. I'm resolving this one.
> Remove Hardcoded Dependency on Hadoop-2.0.3-alpha from YARN and replace with
> a more flexible Maven config
> ---------------------------------------------------------------------------------------------------------
>
> Key: GIRAPH-631
> URL: https://issues.apache.org/jira/browse/GIRAPH-631
> Project: Giraph
> Issue Type: Improvement
> Components: conf and scripts
> Affects Versions: 1.0.0, 1.1.0
> Reporter: Eli Reisman
> Assignee: Eli Reisman
> Fix For: 1.0.0, 1.1.0
>
>
> Currently, Giraph's YARN profile is hardcoded to Version 2.0.3-alpha of
> Hadoop. This is because of two problems:
> 1. Simply creating profiles that can "coexist" such as Hadoop's own
> -Pdist,native type mvn calls is not possible for us since we use munging and
> excludes in Maven to prevent compilation of the YARN code where the deps are
> not included (many profiles) and these excludes don't seem overridable. This
> has been documented online as a Maven "feature" already.
> 2. Simply resetting hadoop.version for the Maven build using a -D option
> should work and should probably be the right fix for us but in the brief time
> I played with it (and with our versioning story that affects backporting not
> decided yet) I did not get it to work myself for Giraph-13 (this is all
> documented there)
> Option 2 will look like:
> {code}
> mvn -Phadoop_yarn -Dhadoop.version=YOUR_FAVORITE_YARNY_HADOOP clean install
> {code}
--
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
