phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alicia Ying Shu (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-2221) Option to make data regions not writable when index regions are not available
Date Sun, 27 Dec 2015 23:26:49 GMT


Alicia Ying Shu commented on PHOENIX-2221:

[~jamestaylor] In, I used the following call to try to get CATALOG table
to check INDEX_DISABLE_TIMESTAMP, but got TableNotFoundException. Is there another way to
get CATALOG table in RegionCoprocessorEnvironment (env) is not presented

HTableInterface systemTable = this.getConnection().getQueryServices().getTable(PhoenixDatabaseMetaData.SYSTEM_CATALOG_TABLE_BYTES);

> Option to make data regions not writable when index regions are not available
> -----------------------------------------------------------------------------
>                 Key: PHOENIX-2221
>                 URL:
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Devaraj Das
>            Assignee: Alicia Ying Shu
>             Fix For: 4.7.0
>         Attachments: PHOENIX-2221-v1.patch, PHOENIX-2221-v2.patch, PHOENIX-2221-v3.patch,
> In one usecase, it was deemed better to not accept writes when the index regions are
unavailable for any reason (as opposed to disabling the index and the queries doing bigger
data-table scans).
> The idea is that the index regions are kept consistent with the data regions, and when
a query runs against the index regions, one can be reasonably sure that the query ran with
the most recent data in the data regions. When the index regions are unavailable, the writes
to the data table are rejected. Read queries off of the index regions would have deterministic
performance (and on the other hand if the index is disabled, then the read queries would have
to go to the data regions until the indexes are rebuilt, and the queries would suffer).

This message was sent by Atlassian JIRA

View raw message