[
https://issues.apache.org/jira/browse/PHOENIX-4278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17749834#comment-17749834
]
ASF GitHub Bot commented on PHOENIX-4278:
-----------------------------------------
stoty closed pull request #291: [PHOENIX-4278] Implement pure client side
transactional index mainten…
URL: https://github.com/apache/phoenix/pull/291
> Implement pure client side transactional index maintenance
> ----------------------------------------------------------
>
> Key: PHOENIX-4278
> URL: https://issues.apache.org/jira/browse/PHOENIX-4278
> Project: Phoenix
> Issue Type: Improvement
> Reporter: James R. Taylor
> Assignee: Ohad Shaham
> Priority: Major
> Fix For: 4.14.0, 5.0.0
>
> Attachments: PHOENIX-4278.4.x-HBase-1.3.v1.patch,
> PHOENIX-4278_5.x-HBase-2.0.patch, PHOENIX-4278_addendum1.patch,
> PHOENIX-4278_v2.patch
>
>
> The index maintenance for transactions follows the same model as non
> transactional tables - coprocessor based on data table updates that looks up
> previous row value to perform maintenance. This is necessary for non
> transactional tables to ensure the rows are locked so that a consistent view
> may be obtained. However, for transactional tables, the time stamp oracle
> ensures uniqueness of time stamps (via transaction IDs) and the filtering
> handles a scan seeing the "true" last committed value for a row. Thus,
> there's no hard dependency to perform this on the server side.
> Moving the index maintenance to the client side would prevent any RS->RS RPC
> calls (which have proved to be troublesome for HBase). It would require
> returning more data to the client (i.e. the prior row value), but this seems
> like a reasonable tradeoff.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
