Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-55744803
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20387/consoleFull)
for PR 1113 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-55744971
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/20387/consoleFull)
for PR 1113 at commit
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1113#discussion_r17454306
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/DriverRunner.scala ---
@@ -139,28 +139,32 @@ private[spark] class DriverRunner(
*
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/1113#discussion_r17454349
--- Diff:
core/src/main/scala/org/apache/spark/deploy/worker/DriverRunner.scala ---
@@ -139,28 +139,32 @@ private[spark] class DriverRunner(
*
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-55340219
@lianhuiwang Yes, have you looked at SparkSubmit? In particular, does the
following do what you want:
```
bin/spark-submit --master standalone --deploy-mode
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54457835
@JoshRosen @andrewor14 I have update comment. has any question for it?
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54562091
Could you add `[SPARK-2301]` to the title? This will help us organize PRs
and link them to JIRAs properly.
---
If your project is set up for it, you can reply to
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54379494
Thanks for opening a JIRA, but do you mind editing it to actually describe
the motivation for this feature? The current JIRA just duplicates the title of
this PR,
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54380213
@lianhuiwang Is the motivation for this such that all additional jars (that
would be passed through `--jars` through spark-submit, for instance) need not
be visible
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-54380405
My understanding is that if we launch something in `standalone-cluster`
mode and our driver uses additional jars, then we need to make sure all the
slave nodes on the
Github user lianhuiwang commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-50126195
@andrewor14 can you take a look at this? thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47295220
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47295238
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47297725
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/16176/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-47297724
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
Github user xiajunluan commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46537162
you could open a JIRA issue to describe you request.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
GitHub user lianhuiwang opened a pull request:
https://github.com/apache/spark/pull/1113
add ability to submit multiple jars for Driver
add ability to submit multiple jars for Driver
You can merge this pull request into a Git repository by running:
$ git pull
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46413148
Merged build triggered.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46413162
Merged build started.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46416660
All automated tests passed.
Refer to this link for build results:
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/15871/
---
If your
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/1113#issuecomment-46416659
Merged build finished. All automated tests passed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well.
21 matches
Mail list logo
