[
https://issues.apache.org/jira/browse/HBASE-7141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494776#comment-13494776
]
Lars Hofhansl commented on HBASE-7141:
--------------------------------------
Probably. The reason why I did not do that when I introduced Mutation was the
the difference in which Increment handles its familyMap. All other mutations
have a map from CF -> Set of KV. Increments maps from CF -> map of Column ->
long.
If there's a good way to unify that, I'd love to do that. 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.
> 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)
> 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
