[jira] [Commented] (HIVE-7692) when table is dropped associated indexes also should be dropped

["Daisy.Yuan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HIVE-7692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14195637#comment-14195637 ] 

Daisy.Yuan commented on HIVE-7692:
----------------------------------

This is a problem. When index table was stored in HBase, but HiveMetaStore (drop_table_core), when hive meta store dropt tables. it dropt indexs first, and just deleted the index table location dir.

But in HiveMetaStoreClient, when it dropt index, it will drop index table first. it get the index table's storagehandler.commitDropTable  and really drop index table data.

> when table is dropped associated indexes also should be dropped
> ---------------------------------------------------------------
>
>                 Key: HIVE-7692
>                 URL: https://issues.apache.org/jira/browse/HIVE-7692
>             Project: Hive
>          Issue Type: Bug
>          Components: Indexing
>            Reporter: Thejas M Nair
>            Assignee: Thejas M Nair
>
> When a table is dropped, any associated indexes should also be dropped. It does not make sense to have these dangling indexes.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)