phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas D'Silva (JIRA)" <j...@apache.org>
Subject [jira] [Issue Comment Deleted] (PHOENIX-2051) Link record is in the format CHILD-PARENT for phoenix views and it has to scan the entire table to find the parent suffix.
Date Tue, 14 Mar 2017 21:53:41 GMT

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

Thomas D'Silva updated PHOENIX-2051:
------------------------------------
    Comment: was deleted

(was: Sure, I based the branch  of 4.x-HBase-0.98 , should I switch it to master?)

> Link record is in the format CHILD-PARENT for phoenix views and it has to scan the entire
table to find the parent suffix.
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: PHOENIX-2051
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2051
>             Project: Phoenix
>          Issue Type: Sub-task
>    Affects Versions: 4.3.1
>            Reporter: Arun Kumaran Sabtharishi
>            Assignee: Thomas D'Silva
>         Attachments: PHOENIX-2051.patch
>
>
> When a phoenix view is dropped, it runs a scan on the SYSTEM.CATALOG table looking for
the link record. Since the link record is in the format CHILD-PARENT, it has to scan the entire
table to find the parent suffix. For the long term solution, we can write two link records,
the existing CHILD-PARENT and a new PARENT-CHILD so that the findChildViews() method can use
a key range scan.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message