Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9278#issuecomment-151094624
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/9278#issuecomment-151094516
[Test build #44346 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44346/console)
for PR 9278 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9278#issuecomment-151094622
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 project does
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/9278#issuecomment-151049644
[Test build #44346 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/44346/consoleFull)
for PR 9278 at commit
GitHub user adrian-wang opened a pull request:
https://github.com/apache/spark/pull/9278
[SPARK-11312][SQL]drop temporary function should match with create
temporary function
create temporary function is done by executionHive, while DROP TEMPORARY
FUNCTION is done by metadataHive,
Github user adrian-wang closed the pull request at:
https://github.com/apache/spark/pull/9278
---
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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/9278#issuecomment-151048998
Build started.
---
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/9278#issuecomment-151048991
Build triggered.
---
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
