[
https://issues.apache.org/jira/browse/SPARK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14119373#comment-14119373
]
Evan Chan commented on SPARK-3298:
----------------------------------
I can't really think of a good way to prevent people from overwriting their
registered tables though without breaking the API..... :/ SQL users
would be used to getting an error if you CREATE TABLE'd on the same name.
Guess this is not quite the same thing, but I would think most API users would
not expect just success. I suppose you can have a config option to make it
silently fail if the table already exists, but this is no better than the
existing behavior....
> [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-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
