Description
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?
Attachments
Issue Links
- relates to
-
SPARK-3212 Improve the clarity of caching semantics
-
- Resolved
-
- links to