Github user srowen commented on the issue:
https://github.com/apache/spark/pull/22466
Owp, I've been misreading that several times. Right. Well by analogy, if a
database has a non default LOCATION then so do it's tables, and they are
treated like EXTERNAL tables. Dropping the DB means dropping the tables, and
dropping those tables doesn't delete data. So should the same happen for DBs?
Seems sensible, because the DB directory might not even be empty.
Still I feel like I'm missing something if it only comes up in the case
that two DBs have the same location, which is going to cause a bunch of other
problems.
But is it the right change simply because it's consistent with how dropping
tables works?
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
