[IMPALA-2518] DROP DATABASE CASCADE does not remove cache directives of tables

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: Impala 2.2.4
• Fix Version/s: Impala 2.9.0
• Component/s: Catalog
• Labels: catalog-server usability
• Target Version: Impala 2.9.0
• Assignee: Dimitris Tsirogiannis
• Reporter: Dimitris Tsirogiannis
• Created: 09/Oct/15 05:39
• Updated: 20/Mar/17 19:52
• Resolved: 20/Mar/17 18:12

Description

Executing a DROP DATABASE statement with the CASCADE option does not clear the cache directives associated with the cached tables that are contained in the dropped database.

To reproduce:

impala> create database foo;
impala> use foo;
impala>create table t1 (a int) cached in 'testPool' with replication = 8;
shell> hdfs cacheadmin -listDirectives
impala> use default;
impala> drop database foo cascade;
shell> hdfs cachedmin -listDirectives <-- the output contains the directive associated with the path of table t1

This has been breaking impala-cdh5.5.x-repeated-runs (https://issues.cloudera.org/browse/IMPALA-2510)