Skip to content

[SPARK-4652][DOCS] Add docs about spark-git-repo option #3513

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

[SPARK-4652][DOCS] Add docs about spark-git-repo option #3513

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
cfaf9be
Add docs about spark-git-repo option
Lewuathe Nov 29, 2014
6dae8ee
Wrap consistent with other descriptions
Lewuathe Nov 30, 2014
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/ec2-scripts.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,6 +85,11 @@ another.
specified version of Spark. The `<version>` can be a version number
(e.g. "0.7.3") or a specific git hash. By default, a recent
version will be used.
- `--spark-git-repo=<repository url>` enables you to run your
development version on EC2 cluster. You need to set
`--spark-version` as git commit hash such as 317e114 not
original release version number. By default, this repository is
set [apache mirror](https://github.com/apache/spark).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Apache" needs to be capitalized here. I'd also swap the order of these sentences so that the default for --spark-git-repo appears first, followed by the sentence describing how --spark-version needs to be set when using this option.

- If one of your launches fails due to e.g. not having the right
permissions on your private key file, you can run `launch` with the
`--resume` option to restart the setup process on an existing cluster.
Expand Down