Github user tejasapatil commented on a diff in the pull request:
https://github.com/apache/spark/pull/13302#discussion_r64687912
--- Diff:
sql/core/src/main/scala/org/apache/spark/sql/execution/command/tables.scala ---
@@ -288,9 +288,10 @@ case class TruncateTableCommand(
override def run(sparkSession: SparkSession): Seq[Row] = {
val catalog = sparkSession.sessionState.catalog
if (!catalog.tableExists(tableName)) {
- logError(s"table '$tableName' in TRUNCATE TABLE does not exist.")
+ throw new AnalysisException(s"Table '$tableName' in TRUNCATE TABLE
does not exist.")
--- End diff --
@yhuai : Hive is doing the right thing of not throwing an exception when
`IF EXISTS` keyword is used in `DROP TABLE` (irrespective of the table being
there or not). If end user expects exception to be thrown, then one should not
use the `IF EXISTS` in the command. Having `IF EXISTS` helps for writing
pipelines which run daily and one wants "drop if exists or do nothing"
semantics.
---
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 enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
