Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10591#issuecomment-168955273
**[Test build #2323 has
started](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2323/consoleFull)**
for PR 10591 at commit
Github user srowen commented on the pull request:
https://github.com/apache/spark/pull/10591#issuecomment-168954409
These LGTM though yeah would prefer to combine logically similar changes
into one PR like #10592
---
If your project is set up for it, you can reply to this email and
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/10591#issuecomment-168956248
**[Test build #2323 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/NewSparkPullRequestBuilder/2323/consoleFull)**
for PR 10591 at commit
Github user jaceklaskowski commented on the pull request:
https://github.com/apache/spark/pull/10591#issuecomment-168976471
Merged to #10595
---
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 jaceklaskowski closed the pull request at:
https://github.com/apache/spark/pull/10591
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/10591#issuecomment-168924253
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 jaceklaskowski opened a pull request:
https://github.com/apache/spark/pull/10591
[CORE][MINOR] scaladoc fixes
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jaceklaskowski/spark core-scaladoc
Alternatively you can
