You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Xiao Li (JIRA)" <ji...@apache.org> on 2016/06/10 04:08:21 UTC
[jira] [Updated] (SPARK-15838) CACHE TABLE AS SELECT should not
replace the existing Temp Table
[ https://issues.apache.org/jira/browse/SPARK-15838?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Li updated SPARK-15838:
----------------------------
Description:
-Currently, {{CACHE TABLE AS SELECT}} replaces the existing Temp Table, if existed. This behavior is different from `CREATE TABLE` or `CREATE VIEW`. It looks risky.-
Better Error Message When Having Database Name in CACHE TABLE AS SELECT
was:Currently, {{CACHE TABLE AS SELECT}} replaces the existing Temp Table, if existed. This behavior is different from `CREATE TABLE` or `CREATE VIEW`. It looks risky.
> CACHE TABLE AS SELECT should not replace the existing Temp Table
> ----------------------------------------------------------------
>
> Key: SPARK-15838
> URL: https://issues.apache.org/jira/browse/SPARK-15838
> Project: Spark
> Issue Type: Bug
> Components: SQL
> Affects Versions: 2.0.0
> Reporter: Xiao Li
>
> -Currently, {{CACHE TABLE AS SELECT}} replaces the existing Temp Table, if existed. This behavior is different from `CREATE TABLE` or `CREATE VIEW`. It looks risky.-
> Better Error Message When Having Database Name in CACHE TABLE AS SELECT
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org