Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/2763
---
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/2763#issuecomment-58848203
Wow, good catch! I'm very surprised that this problem wasn't caught
earlier. I'm going to merge this into `master` and look into backporting it to
the other branches.
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2763#issuecomment-58743286
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/2
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2763#issuecomment-58743282
[QA tests have
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21639/consoleFull)
for PR 2763 at commit
[`17d7990`](https://github.com/a
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/2763#issuecomment-58741865
[QA tests have
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/21639/consoleFull)
for PR 2763 at commit
[`17d7990`](https://github.com/ap
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/2763#issuecomment-58741803
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
