[
https://issues.apache.org/jira/browse/PHOENIX-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14933271#comment-14933271
]
Rajeshbabu Chintaguntla commented on PHOENIX-2221:
--------------------------------------------------
bq. Yes. It is required to partially build the index
It's not clear to me why to build partially build the index when no writes
happened to both data and index tables once state changed to READABLE.
Even though you introduced ReadableIndexFailurePolicy you have added the most
of the checks related to READABLE in PhoenixIndexFailurePolicy. It would be
better to have method accepts index state and in case of
PhoenixIndexFailurePolicy pass DISABLE state and in case of
ReadableIndexFailurePolicy pass READABLE state.
> 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: Alicia Ying Shu
> Attachments: PHOENIX-2221-v1.patch, PHOENIX-2221.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)
