[
https://issues.apache.org/jira/browse/HBASE-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13486381#comment-13486381
]
Jean-Daniel Cryans commented on HBASE-4583:
-------------------------------------------
bq. Why are Puts not doing upserts? And why would we care less about the
history of an increment column?
Most of the Increment workloads I know about are usually trying to push a lot
more ops/sec than puts, which in turn generates both MemStore and HLog garbage.
The way we currently upsert in the MemStore is saving us from flushing hundreds
of GBs of crap than then needs to be compacted.
As to if we should do upsert for Puts... good question, I guess we could permit
that.
> Integrate RWCC with Append and Increment operations
> ---------------------------------------------------
>
> Key: HBASE-4583
> URL: https://issues.apache.org/jira/browse/HBASE-4583
> Project: HBase
> Issue Type: Bug
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 0.94.3, 0.96.0
>
> Attachments: 4583-trunk-radical.txt, 4583-trunk-radical_v2.txt,
> 4583-trunk-v3.txt, 4583.txt, 4583-v2.txt, 4583-v3.txt, 4583-v4.txt
>
>
> Currently Increment and Append operations do not work with RWCC and hence a
> client could see the results of multiple such operation mixed in the same
> Get/Scan.
> The semantics might be a bit more interesting here as upsert adds and removes
> to and from the memstore.
--
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
