[
https://issues.apache.org/jira/browse/PHOENIX-5025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16702281#comment-16702281
]
Kadir OZDEMIR commented on PHOENIX-5025:
----------------------------------------
I have made the following additions to the tool, and update the doc and PR
accordingly
# The orphan view definition is expanded to include missing or incorrect
PARENT_TABLE and CHILD_TABLE links in addition to PHYSICAL_TABLE links
# The tool also identifies and removes the orphan links now in addition to
orphan views
# It takes snapshots of system tables (catalog and child_link tables) before
attempting remove any views or links
# An new option, -a (-- age), to set the minimum age for views and links. The
default value is 1 day.
> Tool to clean up orphan views
> -----------------------------
>
> Key: PHOENIX-5025
> URL: https://issues.apache.org/jira/browse/PHOENIX-5025
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
>
> A view without its base table is an orphan view. Since views are virtual
> tables and their data is stored in their base tables, they are useless when
> they become orphan. A base table can have child views, grandchild views and
> so on. Due to some reasons/bugs, when a base table was dropped, its views
> were not not properly cleaned up in the past. For example, the drop table
> code did not support cleaning up grandchild views. This has been recently
> fixed by PHOENIX-4764. Although PHOENIX-4764 prevents new orphan views due to
> table drop operations, it does not clean up existing orphan views. It is also
> believed that when the system catalog table was split due to a bug in the
> past, it also contributed to creating orphan views as Phoenix did not support
> splittable system catalog. Therefore, Phoenix needs a tool to clean up orphan
> views.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
