You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Michael Armbrust (JIRA)" <ji...@apache.org> on 2015/05/22 00:32:17 UTC

[jira] [Resolved] (SPARK-3298) [SQL] registerAsTable / registerTempTable overwrites old tables

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

Michael Armbrust resolved SPARK-3298.
-------------------------------------
    Resolution: Won't Fix

As discussed above we can't actually make this change without breaking existing user code. As a result, I think we are stuck with the existing behavior and should close this issue unless there is a really compelling reason for the complexity of a configuration flag.  If someone has a compelling production use case for this flag, please open a new JIRA that proposes adding it.

> [SQL] registerAsTable / registerTempTable overwrites old tables
> ---------------------------------------------------------------
>
>                 Key: SPARK-3298
>                 URL: https://issues.apache.org/jira/browse/SPARK-3298
>             Project: Spark
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 1.0.2
>            Reporter: Evan Chan
>            Priority: Minor
>              Labels: newbie
>
> At least in Spark 1.0.2,  calling registerAsTable("a") when "a" had been registered before does not cause an error.  However, there is no way to access the old table, even though it may be cached and taking up space.
> How about at least throwing an error?



--
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