You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Andrew Kyle Purtell (Jira)" <ji...@apache.org> on 2022/06/13 15:32:00 UTC

[jira] [Resolved] (HBASE-10623) Add ability to read a row after applying a RowMutation

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

Andrew Kyle Purtell resolved HBASE-10623.
-----------------------------------------
    Resolution: Won't Fix

> Add ability to read a row after applying a RowMutation
> ------------------------------------------------------
>
>                 Key: HBASE-10623
>                 URL: https://issues.apache.org/jira/browse/HBASE-10623
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Michael Webster
>            Priority: Minor
>
> It would be useful to be able to return a row to the user after all of the mutations in a RowMutation operation has been applied.  This would be similar to transactions in Redis where the result of executing an operation is returned to the user.  However, since RowMutations only affect a single row, only the final result would need to be returned.  This could allow for a snapshot view of the row without requiring any timestamp manipulation, or a second read by the client.
> Looking at the implementation of RowMutations, it seems like the Get could be done after the write has been committed but before the row locks are released.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)