Github user quasiben commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-158090390
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 your project does not have this feature
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-152292218
This is updated by #9179
---
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 quasiben commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-152285739
Was this officially documented ?
---
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
Github user davies commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-116875643
LGTM. We can document this later.
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-116846095
@davies @shivaram any updates on this?
---
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
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-116887043
OK merging into master.
---
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
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/6557
---
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 feature is
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107690706
Can one of the admins verify this patch?
---
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
GitHub user msannell opened a pull request:
https://github.com/apache/spark/pull/6557
[SPARK-8019] [SPARKR] Support SparkR spawning worker R processes with a
command other then Rscript
This is a simple change to add a new environment variable
spark.sparkr.r.command that
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107695620
Jenkins, ok to test
---
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
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107701050
Thanks @msannell for the change.
@davies -- In python we use an environment variable `PYSPARK_PYTHON` to do
this. Any reason we should use an environment
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107703347
[Test build #866 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/866/consoleFull)
for PR 6557 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107696775
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107700045
[Test build #33916 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33916/consoleFull)
for PR 6557 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107700053
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
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107696881
[Test build #33916 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33916/consoleFull)
for PR 6557 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107696759
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 davies commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107707857
SparkConf is the consistent way to manage configurations, we are moving
away from environment variables since Spark 1.0, but still keep compatibility
for old environment
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107726937
[Test build #866 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/866/consoleFull)
for PR 6557 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107731754
[Test build #33925 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33925/consoleFull)
for PR 6557 at commit
Github user shivaram commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107729714
Jenkins, retest this please
---
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/6557#issuecomment-107730280
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/6557#issuecomment-107730244
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 msannell commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107735239
In my work, I haven't used spark-submit: I start R (or TERR), and
access SparkR from there.
Note that SPARKR_DRIVER_R defaults to R, whereas my proposed
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107749265
[Test build #33925 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33925/consoleFull)
for PR 6557 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/6557#issuecomment-107749284
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
26 matches
Mail list logo
