Github user adrian-wang commented on the issue:
https://github.com/apache/spark/pull/15011
@hvanhovell I have checked with Hive and MySQL, they all support dropping
current database. By asking user to switch to another database before drop the
current one is not enough though, if there are multiple users connected to the
same metadata, even you are not using the certain database, some one else may
be using that. What's more, if you want to drop a database but without the
privilege to access databases created by other user, you will always leave one
empty database behind.
In Spark's implementation, we ensure the database exists before we do
anything, so drop current database is OK. This is also the way other systems
adopt.
---
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]
