You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Xu Cang (JIRA)" <ji...@apache.org> on 2019/01/26 00:30:00 UTC

[jira] [Assigned] (PHOENIX-1160) Allow an index to be declared as immutable

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

Xu Cang reassigned PHOENIX-1160:
--------------------------------

    Assignee:     (was: Xu Cang)

> Allow an index to be declared as immutable
> ------------------------------------------
>
>                 Key: PHOENIX-1160
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1160
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Priority: Major
>         Attachments: PHOENIX-1160.WIP.patch
>
>
> Currently, a table must be marked as immutable, through the IMMUTABLE_ROWS=true property specified at creation time. In this case, all indexes added to the table are immutable, while without this property, all indexes are mutable.
> Instead, we should support a mix of immutable and mutable indexes. We already have an INDEX_TYPE field on our metadata row. We can add a new IMMUTABLE keyword and specify an index is immutable like this:
> {code}
> CREATE IMMUTABLE INDEX foo ON bar(c2, c1);
> {code}
> It would be up to the application developer to ensure that only columns that don't mutate are part of an immutable index (we already rely on this anyway).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)