Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206980906
**[Test build #55227 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55227/consoleFull)**
for PR 12146 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206954070
**[Test build #55223 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55223/consoleFull)**
for PR 12146 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206954470
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/12146#issuecomment-206954473
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/12146#issuecomment-206919257
**[Test build #55223 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55223/consoleFull)**
for PR 12146 at commit
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206749551
Test FAILed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206749548
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206749502
**[Test build #55200 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55200/consoleFull)**
for PR 12146 at commit
Github user SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206741814
**[Test build #55200 has
started](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/55200/consoleFull)**
for PR 12146 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206568430
Will catch it and log the error message, like
```scala
case e: org.apache.spark.sql.AnalysisException
if
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206560036
Found the cause. Hive behaves differently. When using Hive Native SQL
command, we did not get an exception from Hive when the table does not exist,
but an error log
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-206396067
Weird...
```scala
try {
if (isView) {
hiveContext.runSqlHive(s"DROP VIEW
$ifExistsClause${tableName.quotedString}")
}
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659279
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +47,38 @@ case class AnalyzeTable(tableName: String)
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659242
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -68,10 +91,14 @@ case class DropTable(
// Users
Github user gatorsmile commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58659065
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +48,40 @@ case class AnalyzeTable(tableName: String)
Github user yhuai commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58649986
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/HiveSqlParser.scala
---
@@ -113,7 +113,10 @@ class HiveSqlAstBuilder extends
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58634134
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +48,40 @@ case class AnalyzeTable(tableName: String)
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58634059
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +48,40 @@ case class AnalyzeTable(tableName: String)
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58632900
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/HiveSqlParser.scala
---
@@ -113,7 +113,10 @@ class HiveSqlAstBuilder extends
Github user andrewor14 commented on a diff in the pull request:
https://github.com/apache/spark/pull/12146#discussion_r58632748
--- Diff:
sql/hive/src/main/scala/org/apache/spark/sql/hive/execution/commands.scala ---
@@ -47,18 +47,38 @@ case class AnalyzeTable(tableName: String)
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-205866052
Test PASSed.
Refer to this link for build results (access rights to CI server needed):
Github user AmplabJenkins commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-205866050
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 SparkQA commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-205865589
**[Test build #54985 has
finished](https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/54985/consoleFull)**
for PR 12146 at commit
Github user gatorsmile commented on the pull request:
https://github.com/apache/spark/pull/12146#issuecomment-205861283
@yhuai Sure, will do it in this PR. 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
24 matches
Mail list logo
