Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80943514
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80943719
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 feature
Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/5032
---
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/5032#issuecomment-80983327
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80983323
[Test build #28624 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28624/consoleFull)
for PR 5032 at commit
GitHub user OopsOutOfMemory opened a pull request:
https://github.com/apache/spark/pull/5032
[SPARK-6285][SQL]Remove ParquetTestData in SparkBuild.scala and in README.md
This is a following clean up PR for #5010
This will resolve issues when launching `hive/console` like below:
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80946011
[Test build #28624 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/28624/consoleFull)
for PR 5032 at commit
Github user OopsOutOfMemory commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80944151
ok, thanks @liancheng
---
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 liancheng commented on the pull request:
https://github.com/apache/spark/pull/5032#issuecomment-80943973
This LGTM. Thanks for fixing this! I can merge it after it passes Jenkins
---
If your project is set up for it, you can reply to this email and have your
reply appear