[ https://issues.apache.org/jira/browse/SPARK-3298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14290962#comment-14290962 ]
Imran Rashid commented on SPARK-3298: ------------------------------------- If {{allowOverwrite}} defaulted to {{true}}, wouldn't that be closer to keeping the existing behavior, but still allow someone to request the check if they wanted it? Maybe I don't properly understand the current behavior, but it seems like it will effectively uncache the existing table and create a new one (even if the uncaching is happening later by the context cleaner). > [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