[
https://issues.apache.org/jira/browse/IMPALA-2518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dimitris Tsirogiannis resolved IMPALA-2518.
-------------------------------------------
Resolution: Fixed
Fix Version/s: Impala 2.8.0
Change-Id: I83ef5a33e06728c2b3f833a0309d9da64dce7b88
Reviewed-on: http://gerrit.cloudera.org:8080/5815
Reviewed-by: Dimitris Tsirogiannis <dtsirogian...@cloudera.com>
Tested-by: Impala Public Jenkins
---
M fe/src/main/java/org/apache/impala/service/CatalogOpExecutor.java
M fe/src/main/java/org/apache/impala/util/HdfsCachingUtil.java
M tests/query_test/test_hdfs_caching.py
3 files changed, 66 insertions(+), 34 deletions(-)
Approvals:
Impala Public Jenkins: Verified
Dimitris Tsirogiannis: Looks good to me, approved
> 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)
