[
https://issues.apache.org/jira/browse/HBASE-10623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13914912#comment-13914912
]
stack commented on HBASE-10623:
-------------------------------
What is your use case Michael? I can understand reading back Increments or
Appends but not sure why for anything else? Yes, it looks like it should be
easy to add as an attribute on the multi row mutation call. Thanks.
> 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
(v6.1.5#6160)
