[
https://issues.apache.org/jira/browse/IMPALA-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15933328#comment-15933328
]
Jim Apple commented on IMPALA-2518:
-----------------------------------
Are you sure this was resolved by 2.8?
https://github.com/apache/incubator-impala/tree/2.8.0
> DROP DATABASE CASCADE does not remove cache directives of tables
> ----------------------------------------------------------------
>
> Key: IMPALA-2518
> URL: https://issues.apache.org/jira/browse/IMPALA-2518
> Project: IMPALA
> Issue Type: Bug
> Components: Catalog
> Affects Versions: Impala 2.2.4
> Reporter: Dimitris Tsirogiannis
> Assignee: Dimitris Tsirogiannis
> Priority: Critical
> Labels: catalog-server, usability
> Fix For: Impala 2.8.0
>
>
> 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:
> {code}
> 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
> {code}
> This has been breaking impala-cdh5.5.x-repeated-runs
> (https://issues.cloudera.org/browse/IMPALA-2510)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
