hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3434) ability to increment a counter without reading original value from storage
Date Thu, 24 Mar 2016 19:14:25 GMT

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

stack commented on HBASE-3434:

Dump it in here [~jmspaggi]

Also to consider is doing increments with CRDTs. See comment here https://issues.apache.org/jira/browse/HBASE-14460?focusedCommentId=14909404&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14909404

If CRDT, could do for increments only but would be sweet if other read-modify-write ops were
at least considered in design of CRDT support.

> 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: stack
>              Labels: gsoc2016, mentor
> 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 was sent by Atlassian JIRA

View raw message