[jira] [Comment Edited] (PHOENIX-4764) Cleanup metadata of child views for a base table that has been dropped

["Bin Shi (JIRA)" <ji...@apache.org>]

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

Bin Shi edited comment on PHOENIX-4764 at 9/21/18 10:40 PM:
------------------------------------------------------------

Regarding "If we try to recreate a base table that was previously dropped but whose child view metadata wasn't cleaned up throw an exception" and "If we try to recreate a table that was previously dropped we then try to drop the child views", when we "recreate" a table that was previously dropped, in HBase/Phoenix, is it possible to treat the new created table to be a different table from the table that was previously dropped, even they have the same namespace and table name? The new table can have a unique internal identifier, such as a global sequential number or GUID, to differentiate from the table that was previously dropped. The benefit of doing this is that, once a table is dropped, cleaning up its orphan child views and recreating a new table with the same name are totally independent which results in simplicity and less chance for throwing errors.


was (Author: bin shi):
Regarding "If we try to recreate a base table that was previously dropped but whose child view metadata wasn't cleaned up throw an exception" and "If we try to recreate a table that was previously dropped we then try to drop the child views", when we "recreate" a table that was previously dropped, in HBase/Phoenix, is it possible to treat the new created table to be a different table from the table that was previously dropped, even they have the same namespace and table name? The new table can have a unique internal identifier, such as a global sequential number or GUID, or to differentiate from the table that was previously dropped. The benefit of doing this is that, once a table is dropped, cleaning up its orphan child views and recreating a new table with the same name are totally independent which results in simplicity and less chance for throwing errors.

> Cleanup metadata of child views for a base table that has been dropped
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-4764
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-4764
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: Thomas D'Silva
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>
> When we drop a base table, we no longer drop all the child view metadata. 
> Clean up the child view metadata during compaction. 
> If we try to recreate a base table that was previously dropped but whose child view metadata wasn't cleaned up throw an exception. Add a test for this. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)