Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of jeff@opower.com designates
 209.85.219.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAG2rwuNaMoMEiXKJuoexKvUh2MfK6F-8rZ87GeGvGd99Vt72fw@mail.gmail.com>
References: 
 <CAG2rwuNaMoMEiXKJuoexKvUh2MfK6F-8rZ87GeGvGd99Vt72fw@mail.gmail.com>
Date: Wed, 6 Mar 2013 13:20:36 -0800
Message-ID: 
 <CACHGzSQjK5=uvZHMoLFVp3FeF5pc6Vp5mZXcJzRjSmUFAWFqjA@mail.gmail.com>
Subject: Re: how do counters work, client api?
From: Jeff Kolesky <jeff@opower.com>
To: user@hbase.apache.org
Content-Type: multipart/alternative; boundary=bcaec554098048500b04d7482932

--bcaec554098048500b04d7482932
Content-Type: text/plain; charset=ISO-8859-1

One interesting post to read is from Lars H:
http://hadoop-hbase.blogspot.com/2012/11/hbase-mvcc-and-built-in-atomic.html
It describes how the atomic counter operations work.

Jeff


On Wed, Mar 6, 2013 at 12:25 PM, S Ahmed <sahmed1020@gmail.com> wrote:

> Where can I read up on how counters work with hbase?
>
> Does it have some sort of api like:
>
> hbaseClient.incrementAndGet()
>
> Since things are distributed, I would imagine actually acting on the
> counter value is not really possible since unless the thing acting on the
> counter is single threaded right?
>


-- 
*Jeff Kolesky*
Chief Software Architect
*Opower*

--bcaec554098048500b04d7482932--