Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/15019
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/15019
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/65125/
Test PASSed.
---
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15019
**[Test build #65125 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65125/consoleFull)**
for PR 15019 at commit
[`100e442`](https://github.com/apache/spark/commit/
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/15019
Ok, I'll close this off then
---
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 an
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15019
> that won't work in the PySpark shell either though, even if you restart
the SparkContext
That's a separate issue which should also be fixed (stopping a python
SparkContext does not stop th
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/15019
Hmmm, that won't work in the PySpark shell either though, even if you
restart the SparkContext. If that's what you want though, @zjffdu 's PR
addresses that.
---
If your project is set up for
Github user vanzin commented on the issue:
https://github.com/apache/spark/pull/15019
@BryanCutler sorry, this is not what I meant. Guess I was confused about
your comment on the bug.
See my original code on the bug:
```
>>> from pyspark import SparkContext
>>
Github user BryanCutler commented on the issue:
https://github.com/apache/spark/pull/15019
@vanzin and @zjffdu , this is my take on a simplified solution that will
allow configuring the JVM from the command line. You still won't be able to
use these confs in the shell when creating t
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/15019
**[Test build #65125 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/65125/consoleFull)**
for PR 15019 at commit
[`100e442`](https://github.com/apache/spark/commit/1
