phoenix-issues mailing list archives

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


Hadoop QA commented on PHOENIX-1160:

{color:red}-1 overall{color}.  Here are the results of testing the latest attachment
  against master branch at commit 1fcc887faac1aaa45c69b70b084a51ef7b8c5df6.
  ATTACHMENT ID: 12937585

    {color:green}+1 @author{color}.  The patch does not contain any @author tags.

    {color:red}-1 tests included{color}.  The patch doesn't appear to include any new or modified
                        Please justify why no new tests are needed for this patch.
                        Also please list what manual steps were performed to verify this patch.

    {color:red}-1 patch{color}.  The patch command could not apply the patch.

Console output:

This message is automatically generated.

> Allow an index to be declared as immutable
> ------------------------------------------
>                 Key: PHOENIX-1160
>                 URL:
>             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

View raw message