Zoltán Borók-Nagy created IMPALA-9069:
-----------------------------------------
Summary: Impala should acquire an ACID lock when dropping a
database
Key: IMPALA-9069
URL: https://issues.apache.org/jira/browse/IMPALA-9069
Project: IMPALA
Issue Type: Bug
Reporter: Zoltán Borók-Nagy
Dropping a table takes an exclusive lock on the table, hence it cannot be
removed while other queries are working on it.
However, dropping a database doesn't take any locks, so it just starts removing
table data even if there are locks on the table by other clients.
Moreover, the Hive Metastore doesn't delete the locks that refer to dropped
entities and when the database and tables are re-created those locks will be
still around (because the locks refer to the databases and tables via their
names).
Impala should acquire an exclusive lock on the database during DROP.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-all-unsubscr...@impala.apache.org
For additional commands, e-mail: issues-all-h...@impala.apache.org
