Github user asfgit closed the pull request at:
https://github.com/apache/spark/pull/13307
---
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 andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221964196
https://issues.apache.org/jira/browse/SPARK-15576
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221963953
OK, let's do that in a follow-up patch. Thanks, merging into master 2.0.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221755462
Merged 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
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221755463
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/13307#issuecomment-221755328
**[Test build #59314 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59314/consoleFull)**
for PR 13307 at commit
Github user yhuai commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221753653
Seems we should convert those disabled tests to our tests? Or we should put
those disabled tests to HiveQuerySuite or HiveWindowFunctionQuerySuite?
---
If your project
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221751101
@yhuai
---
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221744328
**[Test build #59314 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59314/consoleFull)**
for PR 13307 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221736983
**[Test build #59302 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59302/consoleFull)**
for PR 13307 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221737088
Merged build finished. Test FAILed.
---
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 AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221737102
Test FAILed.
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/13307#issuecomment-221726723
**[Test build #59302 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/59302/consoleFull)**
for PR 13307 at commit
GitHub user andrewor14 opened a pull request:
https://github.com/apache/spark/pull/13307
[SPARK-15539][SQL] DROP TABLE throw exception if table doesn't exist
## What changes were proposed in this pull request?
Same as #13302, but for DROP TABLE.
## How was this
Github user andrewor14 commented on the pull request:
https://github.com/apache/spark/pull/13307#issuecomment-221726577
@hvanhovell
---
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
15 matches
Mail list logo
