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

Posted to issues@phoenix.apache.org by "Viraj Jasani (Jira)" <ji...@apache.org> on 2025/12/08 08:01:00 UTC

[jira] [Commented] (PHOENIX-7364) Make phoenix.updatable.view.restriction.enabled a table level property

    [ https://issues.apache.org/jira/browse/PHOENIX-7364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18043470#comment-18043470 ] 

Viraj Jasani commented on PHOENIX-7364:
---------------------------------------

Similar to how we can set or unset maxLookback config using CREATE TABLE and ALTER TABLE statements, we can do the same for "phoenix.updatable.view.restriction.enabled" also. We don't need to create new column in SYSTEM.CATALOG for it.

> Make phoenix.updatable.view.restriction.enabled a table level property
> ----------------------------------------------------------------------
>
>                 Key: PHOENIX-7364
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-7364
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Jacob Isaac
>            Assignee: Jing Yu
>            Priority: Major
>
> The PHOENIX-4555 specifications allow views to be created with certain constraints and conditions.
> It would make sense for this to be a table property so that it gives users more flexibility. When defined for an existing table the upgrade path for the table should ensure that all views under this table should conform to spec. We should store that state (view restriction enabled and verified) in the table header. So that we do not have to do these complete view hierarchy checks for every new view creation



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