[
https://issues.apache.org/jira/browse/HBASE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13495685#comment-13495685
]
Andrew Purtell edited comment on HBASE-7141 at 11/12/12 10:20 PM:
------------------------------------------------------------------
bq. I contemplated have Increment also maintain a map from CF -> Set of KV,
but then there's unnecessary encoding at the client and decoding at the server.
But maybe that is the right way to go.
+1, it's a reasonable tradeoff. Although, it would be enough for my purposes on
HBASE-6222 for Increment to extend OperationWithAttributes.
was (Author: apurtell):
bq. I contemplated have Increment also maintain a map from CF -> Set of
KV, but then there's unnecessary encoding at the client and decoding at the
server. But maybe that is the right way to go.
+1, it's a reasonable tradeoff. Although, it would be enough for my purposed on
HBASE-6222 for Increment to extend OperationWithAttributes.
> Cleanup Increment and Append issues
> -----------------------------------
>
> Key: HBASE-7141
> URL: https://issues.apache.org/jira/browse/HBASE-7141
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Fix For: 0.96.0
>
>
> * Append and Increment should take a TS for their update phase
> * Append should access a timerange for the read phase
> * Increment should no longer implement Writable (in trunk)
> * Increment and Append makes changes visible through the memstore before the
> WAL is sync'ed
> This depends on HBASE-4583
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
