phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (PHOENIX-2221) Option to make data regions not writable when index regions are not available
Date Wed, 27 Jan 2016 22:23:40 GMT

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

James Taylor updated PHOENIX-2221:
----------------------------------
    Attachment:     (was: PHOENIX-2221_v7.patch)

> Option to make data regions not writable when index regions are not available
> -----------------------------------------------------------------------------
>
>                 Key: PHOENIX-2221
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-2221
>             Project: Phoenix
>          Issue Type: Improvement
>            Reporter: Devaraj Das
>            Assignee: James Taylor
>             Fix For: 4.8.0
>
>         Attachments: PHOENIX-2221-v1.patch, PHOENIX-2221-v2.patch, PHOENIX-2221-v3.patch,
PHOENIX-2221-v4.patch, PHOENIX-2221-v5.patch, PHOENIX-2221-v6.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
(v6.3.4#6332)

Mime
View raw message