James Taylor commented on PHOENIX-4278:

Thanks, [~ohads] - I've attached the final version of the patch that handles 
not performing any server-side index maintenance if the client-side is 4.14 or 
higher. This handles the case of existing Tephra transactional tables. I also 
removed the TxState.getUpdateAttributes() as it wasn't used anywhere.

> 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 Taylor
>            Assignee: Ohad Shacham
>            Priority: Major
>         Attachments: PHOENIX-4278.4.x-HBase-1.3.v1.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

Reply via email to