[
https://issues.apache.org/jira/browse/PHOENIX-2221?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14804644#comment-14804644
]
James Taylor commented on PHOENIX-2221:
---------------------------------------
We got a bit distracted with the 4.5.0, 4.5.1 and 4.5.2 releases, but it's
under active development. We've been working with the Tephra community to get
what we need into their release. They've added HBase 1.1 support and have
committed to TEPHRA-89 which will allow an existing table to be altered to
become transactional. Remaining work on our end includes:
- rounding out the testing for table/secondary index consistency in the case of
write failures
- merging back to master
- performance testing
Note for the case of table with immutable rows, the overhead is pretty low, so
I'm not too worried about performance there. It's unclear what kind of overhead
there'll be for mutable data.
I'd estimate we're 3-4 weeks out from completion of the above for a v1. I'm
sure there'll be follow up work to improve performance and ease of operation
(for example TEPHRA-35). One thing to keep in mind too is that transactions are
optional on a table by table basis.
> 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.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)
