Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16077
LGTM. Merging this to master, branch-2.1
---
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 have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16077
Merged build finished. Test PASSed.
---
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 have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16077
**[Test build #69654 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69654/consoleFull)**
for PR 16077 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16077
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69654/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16077
**[Test build #69654 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69654/consoleFull)**
for PR 16077 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16077
Right, I was just reviewing possible code paths for this in the last few
days and I'm pretty confident that this change will not run install.spark in
cluster modes (which would have Spark/JVM
Github user shivaram commented on the issue:
https://github.com/apache/spark/pull/16077
Just to clarify this limits the auto-install feature to SparkR running on
an interactive shell -- Is that right ? I think thats mostly fine as its the
use-case we were targeting but it might good
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16077
LGTM
---
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 have this feature
enabled and wishes so, or if the
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16077
install.spark() checks if SPARK_HOME is set or the Spark Jar can be found
in the cache location.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user yanboliang commented on the issue:
https://github.com/apache/spark/pull/16077
Is this means that it will install spark package each time when starting a
new session in interactive mode? Thanks.
---
If your project is set up for it, you can reply to this email and have
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16077
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69386/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16077
**[Test build #69386 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69386/consoleFull)**
for PR 16077 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/16077
Merged build finished. Test PASSed.
---
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 have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/16077
**[Test build #69386 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/69386/consoleFull)**
for PR 16077 at commit
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/16077
@yanboliang @shivaram
---
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 have this feature
enabled and
15 matches
Mail list logo
