Github user marmbrus commented on the pull request:
https://github.com/apache/spark/pull/4271#issuecomment-72106118
I'm not entirely sure about this change as the semantics are kind of
confusing. Regardless, we should not change the existing behavior and break
all kinds of user code.
The problem is as follows: What does `existing` mean? Is it another
temporary table or a persistent metastore table? Right now we explicitly allow
users to shadow metastore tables with temporary tables. Also temporary tables
aren't scoped to a database so creating one could cause the error state to
change based on what database has been `USE`ed.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
