Github user lianhuiwang commented on the issue:
https://github.com/apache/spark/pull/14154
OK, I close it. Thanks.
---
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
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14154
@lianhuiwang I don't think this necessary. Could you close it? Thanks for
working on it!
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user lianhuiwang commented on the issue:
https://github.com/apache/spark/pull/14154
@hvanhovell I cannot find why Hive support it from
https://issues.apache.org/jira/browse/HIVE-1856.
But now many Spark users have used Hive before, So that make some previous
these queries
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14154
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62169/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14154
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14154
**[Test build #62169 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62169/consoleFull)**
for PR 14154 at commit
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14154
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62168/
Test PASSed.
---
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/14154
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 project does not have this feature
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14154
**[Test build #62168 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62168/consoleFull)**
for PR 14154 at commit
Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/14154
This is by design; we throw exceptions for all invalid commands. Why should
we follow Hive here?
See for more context: https://github.com/apache/spark/pull/13307 &
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14154
**[Test build #62169 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62169/consoleFull)**
for PR 14154 at commit
Github user SparkQA commented on the issue:
https://github.com/apache/spark/pull/14154
**[Test build #62168 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/62168/consoleFull)**
for PR 14154 at commit
12 matches
Mail list logo
