Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15159
**[Test build #65644 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65644/consoleFull)**
for PR 15159 at commit
[`2271887`](https://github.com/apache/spark/commit/2
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15159
**[Test build #65644 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65644/consoleFull)**
for PR 15159 at commit
[`2271887`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15159
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65644/
Test FAILed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15159
Merged build finished. Test FAILed.
---
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
e
Github user felixcheung commented on the issue:
https://github.com/apache/spark/pull/15159
Do you have a test or use case that have both Python and R code? I'm not
quite sure that actually work..
---
If your project is set up for it, you can reply to this email and have your
reply ap
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/15159
@felixcheung Just as I mention in the jira description, zeppelin/livy would
use both pyspark and sparkR. I try this PR with zeppelin (but needs some code
change in zeppelin), and it works.
---
If
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/15159
Add @rxin @davies @JoshRosen @shivaram for more feedback.
---
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 hav
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15159
Just a heads up this has conflicts with master so it might be good to
update (since I know a lot of reviewers use the spark-pr dashboard and maybe
skip PRs which aren't mergable).
---
If your proj
Github user holdenk commented on the issue:
https://github.com/apache/spark/pull/15159
@zjffdu so is the intent of this to allow people to use PySpark from Scala
Spark applications?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user zjffdu commented on the issue:
https://github.com/apache/spark/pull/15159
@holdenk that's correct.
---
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
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15159
**[Test build #66594 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66594/consoleFull)**
for PR 15159 at commit
[`522e3e8`](https://github.com/apache/spark/commit/5
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15159
**[Test build #66594 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/66594/consoleFull)**
for PR 15159 at commit
[`522e3e8`](https://github.com/apache/spark/commit/
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15159
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
e
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15159
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/66594/
Test PASSed.
---
Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15159
(gentle ping @zjffdu)
---
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 wishe
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15159
I wonder if there isn't a better way to handle this without having to add
more configs.
e.g., just distribute things if the user asks for it. For example, if
`--py-files` is provided, distri
16 matches
Mail list logo
