Mailing-List: contact dev-help@hive.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hive.apache.org
Date: Tue, 4 Nov 2014 03:27:34 +0000 (UTC)
From: "Thejas M Nair (JIRA)" <jira@apache.org>
To: hive-dev@hadoop.apache.org
Message-ID: <JIRA.12733531.1407860734000.405705.1415071654016@Atlassian.JIRA>
In-Reply-To: <JIRA.12733531.1407860734000@Atlassian.JIRA>
References: <JIRA.12733531.1407860734000@Atlassian.JIRA>
 <JIRA.12733531.1407860734710@arcas>
Subject: [jira] [Commented] (HIVE-7692) when table is dropped associated
 indexes also should be dropped
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Thejas M Nair commented on HIVE-7692:
-------------------------------------

[~daisy_yu] Not related to the issue you raised ( I will need to dig more into it to understand it better). But your use case of hbase for indexes is interesting. Can you share any more information about it ? Have you found it very useful ? What sort of queries do you see benefiting out of it ?


> 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)