You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Hyukjin Kwon (Jira)" <ji...@apache.org> on 2020/12/06 03:47:00 UTC

[jira] [Resolved] (SPARK-33637) Spark sql drop non-existent table will not report an error after failure

     [ https://issues.apache.org/jira/browse/SPARK-33637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hyukjin Kwon resolved SPARK-33637.
----------------------------------
    Resolution: Invalid

No feedback from the reporter.

> Spark sql drop non-existent table will not report an error after failure
> ------------------------------------------------------------------------
>
>                 Key: SPARK-33637
>                 URL: https://issues.apache.org/jira/browse/SPARK-33637
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 2.4.0
>            Reporter: guihuawen
>            Priority: Major
>
> In the migration of spark sql to hive sql, in order to reduce user changes, spark sql will report an error when executing a table where drop does not exist, but hive sql will not. In order to ensure that the grammar can be executed normally, no error is reported when changing to a table that does not exist in drop.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org