You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Thomas D'Silva (JIRA)" <ji...@apache.org> on 2017/02/17 23:53:44 UTC
[jira] [Updated] (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.
[ https://issues.apache.org/jira/browse/PHOENIX-2051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas D'Silva updated PHOENIX-2051:
------------------------------------
Attachment: PHOENIX-2051.patch
[~jamestaylor]
Can you please review?
> 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)