Skip to content

Conversation

@pwendell
Copy link
Contributor

@pwendell pwendell commented May 9, 2014

Gives a nicely formatted message to the user when run-example is run to
tell them to use spark-submit.

Gives a nicely formatted message to the user when `run-examle` is run to
tell them to use `spark-submit`.
@AmplabJenkins
Copy link

Merged build triggered.

@AmplabJenkins
Copy link

Merged build started.

@pwendell
Copy link
Contributor Author

pwendell commented May 9, 2014

cc/ @andrewor14

@AmplabJenkins
Copy link

Merged build finished. All automated tests passed.

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14832/

bin/run-example Outdated
Copy link
Contributor Author

Choose a reason for hiding this comment

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

I thought about this some more, I think maybe we should just call spark-submit with the supplied master instead of telling the user this stuff. Or we could call spark submit and then print out the user how to run this.

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, I completely agree. We dont want the user to have to type out this more complicated stuff with library path and all. Just

bin/run-example org.apache.examples.spark.SparkPi <example params>

In fact, now that all the examples are inside spark.examples. package, we can try to make it even simpler. To run SparkPi, one should be able to just say

./bin/run-example SparkPi

That would very simple!

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Great idea!

Copy link
Contributor

Choose a reason for hiding this comment

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

well but then you have streaming examples and mllib examples. Do we expect the user to type in millib.MovieLensALS then? I actually think the org.apache.examples.spark.SparkPi is more consistent with the rest (i.e. SparkSubmit). Maybe we should accept both.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yea so I think if it starts with org.apache.spark.examples we would pass it through. If not, we'll prepend org.apache.spark.examples.

@AmplabJenkins
Copy link

Merged build triggered.

@AmplabJenkins
Copy link

Merged build started.

@AmplabJenkins
Copy link

Merged build triggered.

@AmplabJenkins
Copy link

Merged build started.

README.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: What does the notation [< ... >] mean? I think it's clearer if it's just [params]

@AmplabJenkins
Copy link

Merged build finished.

@AmplabJenkins
Copy link

Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14838/

README.md Outdated
Copy link
Contributor

Choose a reason for hiding this comment

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

N threads

@pwendell
Copy link
Contributor Author

pwendell commented May 9, 2014

@andrewor14 great - thanks for the feedback!

@AmplabJenkins
Copy link

Merged build triggered.

@AmplabJenkins
Copy link

Merged build started.

@AmplabJenkins
Copy link

Merged build finished. All automated tests passed.

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14839/

Copy link
Contributor

Choose a reason for hiding this comment

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

oops sorry there's another one

@andrewor14
Copy link
Contributor

Pending one small change this LGTM

@pwendell
Copy link
Contributor Author

pwendell commented May 9, 2014

Okay cool - I'll pull that change in when I merge it.

@AmplabJenkins
Copy link

Merged build finished. All automated tests passed.

@AmplabJenkins
Copy link

All automated tests passed.
Refer to this link for build results: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/14841/

asfgit pushed a commit that referenced this pull request May 9, 2014
Gives a nicely formatted message to the user when `run-example` is run to
tell them to use `spark-submit`.

Author: Patrick Wendell <[email protected]>

Closes #704 from pwendell/examples and squashes the following commits:

1996ee8 [Patrick Wendell] Feedback form Andrew
3eb7803 [Patrick Wendell] Suggestions from TD
2474668 [Patrick Wendell] SPARK-1565 (Addendum): Replace `run-example` with `spark-submit`.
(cherry picked from commit 06b15ba)

Signed-off-by: Patrick Wendell <[email protected]>
@asfgit asfgit closed this in 06b15ba May 9, 2014
aarondav added a commit to aarondav/spark that referenced this pull request May 9, 2014
Looks like this change was accidentally committed here:
apache@06b15ba

but the change does not show up in the PR itself (apache#704).

Other than not intending to go in with that PR, this also broke the test
JavaApiSuite.repartition.
asfgit pushed a commit that referenced this pull request May 9, 2014
Looks like this change was accidentally committed here: 06b15ba
but the change does not show up in the PR itself (#704).

Other than not intending to go in with that PR, this also broke the test JavaAPISuite.repartition.

Author: Aaron Davidson <[email protected]>

Closes #716 from aarondav/shufflerand and squashes the following commits:

b1cf70b [Aaron Davidson] SPARK-1770: Revert accidental(?) fix

(cherry picked from commit 59577df)
Signed-off-by: Aaron Davidson <[email protected]>
asfgit pushed a commit that referenced this pull request May 9, 2014
Looks like this change was accidentally committed here: 06b15ba
but the change does not show up in the PR itself (#704).

Other than not intending to go in with that PR, this also broke the test JavaAPISuite.repartition.

Author: Aaron Davidson <[email protected]>

Closes #716 from aarondav/shufflerand and squashes the following commits:

b1cf70b [Aaron Davidson] SPARK-1770: Revert accidental(?) fix
pdeyhim pushed a commit to pdeyhim/spark-1 that referenced this pull request Jun 25, 2014
Gives a nicely formatted message to the user when `run-example` is run to
tell them to use `spark-submit`.

Author: Patrick Wendell <[email protected]>

Closes apache#704 from pwendell/examples and squashes the following commits:

1996ee8 [Patrick Wendell] Feedback form Andrew
3eb7803 [Patrick Wendell] Suggestions from TD
2474668 [Patrick Wendell] SPARK-1565 (Addendum): Replace `run-example` with `spark-submit`.
pdeyhim pushed a commit to pdeyhim/spark-1 that referenced this pull request Jun 25, 2014
Looks like this change was accidentally committed here: apache@06b15ba
but the change does not show up in the PR itself (apache#704).

Other than not intending to go in with that PR, this also broke the test JavaAPISuite.repartition.

Author: Aaron Davidson <[email protected]>

Closes apache#716 from aarondav/shufflerand and squashes the following commits:

b1cf70b [Aaron Davidson] SPARK-1770: Revert accidental(?) fix
agirish pushed a commit to HPEEzmeral/apache-spark that referenced this pull request May 5, 2022
- update secret and cm names to follow new convention

Co-authored-by: Alexandr Navara <[email protected]>
udaynpusa pushed a commit to mapr/spark that referenced this pull request Jan 30, 2024
- update secret and cm names to follow new convention

Co-authored-by: Alexandr Navara <[email protected]>
mapr-devops pushed a commit to mapr/spark that referenced this pull request May 8, 2025
- update secret and cm names to follow new convention

Co-authored-by: Alexandr Navara <[email protected]>
turboFei pushed a commit to turboFei/spark that referenced this pull request Nov 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants