You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Asaf Mesika (JIRA)" <ji...@apache.org> on 2012/11/14 08:18:13 UTC

[jira] [Commented] (HBASE-3434) ability to increment a counter without reading original value from storage

    [ https://issues.apache.org/jira/browse/HBASE-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13496913#comment-13496913 ] 

Asaf Mesika commented on HBASE-3434:
------------------------------------

Dhurba - did you managed to code this stuff? We've just been hitting the exact same problem. I've seen a very similar design implemented in project [HBaseHUT|https://github.com/sematext/HBaseHUT], but he focused on Puts rather than increments and decided to place code in Client and a M/R job other than using co-processors 
                
> ability to increment a counter without reading original value from storage
> --------------------------------------------------------------------------
>
>                 Key: HBASE-3434
>                 URL: https://issues.apache.org/jira/browse/HBASE-3434
>             Project: HBase
>          Issue Type: Improvement
>          Components: Client, regionserver
>            Reporter: dhruba borthakur
>            Assignee: dhruba borthakur
>
> There are a bunch of applications that do read-modify-write operations on HBase constructs, e.g  a counter; The counter value has to be read in from hdfs before it can be incremented.  We have an application where the number of increments on a counter far outnumbers the number of times the counter is used or read. For these type of applications, it will be very beneficial to not have to read in the counter from disk before it can be incremented.

--
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