Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/10491
---
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 ena
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173606818
Merged to 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 this featu
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173170970
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 a
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173014955
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173014960
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173014806
**[Test build #49710 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49710/consoleFull)**
for PR 10491 at commit
[`94001dd`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173004136
**[Test build #49710 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49710/consoleFull)**
for PR 10491 at commit
[`94001dd`](https://gi
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-173000121
good idea, added spark.driver.memory
---
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
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172793610
Looks reasonable; while we're here, does `running-on-yarn.md` need to
document `spark.driver.memory` for consistency? I see `spark.driver.cores`
documented.
---
If you
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172737699
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172737638
**[Test build #49662 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49662/consoleFull)**
for PR 10491 at commit
[`6983d15`](https://g
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172737697
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 projec
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172736310
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172736309
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172735969
**[Test build #49662 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/49662/consoleFull)**
for PR 10491 at commit
[`6983d15`](https://gi
Github user felixcheung commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-172735041
Thank you for the detailed explanation, @srowen.
Agreed it would be valuable to have a dedicated doc page for CLI flags,
perhaps as a bigger project later. As of
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167759582
I guess my point is that these CLI flags are already documented in the CLI,
as help text.
I can see an argument for formally, separately documenting them in the
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167697099
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167697095
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167696817
**[Test build #48387 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48387/consoleFull)**
for PR 10491 at commit
[`27c6976`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167692412
**[Test build #48387 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48387/consoleFull)**
for PR 10491 at commit
[`27c6976`](https://gi
Github user felixcheung commented on a diff in the pull request:
https://github.com/apache/spark/pull/10491#discussion_r48517225
--- Diff: docs/configuration.md ---
@@ -120,7 +120,8 @@ of the most common options to set are:
spark.driver.cores
1
-Number
Github user srowen commented on a diff in the pull request:
https://github.com/apache/spark/pull/10491#discussion_r48471720
--- Diff: docs/configuration.md ---
@@ -120,7 +120,8 @@ of the most common options to set are:
spark.driver.cores
1
-Number of co
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167473135
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167473131
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 projec
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167472857
**[Test build #48358 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48358/consoleFull)**
for PR 10491 at commit
[`0fb3a40`](https://g
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10491#issuecomment-167469480
**[Test build #48358 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/48358/consoleFull)**
for PR 10491 at commit
[`0fb3a40`](https://gi
GitHub user felixcheung opened a pull request:
https://github.com/apache/spark/pull/10491
[SPARK-12534][DOC] update documentation to list command line equivalent to
properties
Several Spark properties equivalent to Spark submit command line options
are missing.
You can merge this
28 matches
Mail list logo
