phoenix-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vincent Poon (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-1160) Allow an index to be declared as immutable
Date Sat, 26 Jan 2019 00:23:00 GMT


Vincent Poon commented on PHOENIX-1160:

[~kozdemir] this is the jira I was referring to.  Looks like [~xucang] had an initial patch
for this.  Perhaps we can start by reviewing that.

> Allow an index to be declared as immutable
> ------------------------------------------
>                 Key: PHOENIX-1160
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: James Taylor
>            Assignee: Xu Cang
>            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

View raw message