Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2012
---
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 enab
Github user JoshRosen commented on the pull request:
https://github.com/apache/spark/pull/2012#issuecomment-52698755
LGTM; merged into `master` and `branch-1.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 pro
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2012#issuecomment-52573822
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18795/consoleFull)
for PR 2012 at commit
[`e717fb6`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2012#issuecomment-52568243
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/18795/consoleFull)
for PR 2012 at commit
[`e717fb6`](https://github.com/ap
Github user rxin commented on the pull request:
https://github.com/apache/spark/pull/2012#issuecomment-52568033
Jenkins, test 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 have this
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2012#issuecomment-52474725
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 pro
GitHub user hzw19900416 opened a pull request:
https://github.com/apache/spark/pull/2012
Move a bracket in validateSettings of SparkConf
Move a bracket in validateSettings of SparkConf
You can merge this pull request into a Git repository by running:
$ git pull https://github.c
