Uh oh!
There was an error while loading. Please reload this page.
Fix hadoop.version in building-spark.md - #15440
Closed
apivovarov wants to merge 1 commit into
Closed
Conversation
Couple mvn build examples use `-Dhadoop.version=VERSION` instead of actual version number
AmplabJenkins
commented
Oct 11, 2016
Can one of the admins verify this patch? |
rxin
commented
Oct 12, 2016
Contributor
Thanks - merging in master/branch-2.0. |
uzadude pushed a commit
to uzadude/spark
that referenced
this pull request
Jan 27, 2017
Couple of mvn build examples use `-Dhadoop.version=VERSION` instead of actual version number Author: Alexander Pivovarov <apivovarov@gmail.com> Closesapache#15440 from apivovarov/patch-1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Couple of mvn build examples use
-Dhadoop.version=VERSIONinstead of actual version number