You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@phoenix.apache.org by "Kadir OZDEMIR (JIRA)" <ji...@apache.org> on 2019/04/18 06:36:00 UTC

[jira] [Updated] (PHOENIX-5247) DROP TABLE and DROP VIEW commands fail to drop second or higher level child views

     [ https://issues.apache.org/jira/browse/PHOENIX-5247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kadir OZDEMIR updated PHOENIX-5247:
-----------------------------------
    Attachment: PHOENIX-5247.4.14-HBase-1.2.001.patch

> DROP TABLE and DROP VIEW commands fail to drop second or higher level child views
> ---------------------------------------------------------------------------------
>
>                 Key: PHOENIX-5247
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-5247
>             Project: Phoenix
>          Issue Type: Bug
>    Affects Versions: 4.14.2
>            Reporter: Kadir OZDEMIR
>            Assignee: Kadir OZDEMIR
>            Priority: Major
>             Fix For: 4.14.2
>
>         Attachments: PHOENIX-5247.4.14-HBase-1.2.001.patch, PHOENIX-5247.4.14.1-HBase-1.2.001.patch
>
>
> We have seen large number of orphan views in our production environments. The method (doDropTable) that is used to drop tables and views drops only the first level child views of tables. This seems to be the main root cause for orphan views. doDropTable() is recursive only when the table type is TABLE or SYSTEM. The table type for views is VIEW. The findChildViews method returns the first level child views. So, doDropTable ignores dropping views of views (i.e., second or higher level views).



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