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

Posted to dev@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2023/10/12 17:12:00 UTC

[jira] [Assigned] (PHOENIX-7067) View indexes should be created only on non overlapping updatable views

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

Viraj Jasani reassigned PHOENIX-7067:
-------------------------------------

    Assignee: Viraj Jasani

> View indexes should be created only on non overlapping updatable views
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-7067
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7067
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Jacob Isaac
>            Assignee: Viraj Jasani
>            Priority: Major
>
> Updatable views by definition outlined in PHOENIX-4555 are disjoint partitions/virtual tables on the base HBase table.
> View indexes should only be allowed to be defined on these partitions.
> As PHOENIX-7047 revealed index rows are not generated or get clobbered for certain multi-level views.
> This JIRA will try and address these issues and add the proper constraints on when updatable views and view indexes can be created.
> 1. View should be allowed to extend the parent PK i.e. adding its own PK column in the view definition only when there are no indexes in the parent hierarchy.
> and vice versa
> 2. View indexes can defined on a given view only when there are no child views that have extended the PK of the base view.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)