Hi there- I think there are two subjects here:
1) the fact that HTable isn't thread-safe 2) how counters work Even if you are incrementing counters, you shouldn't be sharing HTable instances across threads. Counters get updated atomically on the RS, not on the client. Counter behavior isn't in the Hbase book and it needs to be. I'll add it to the list. On 7/20/11 7:44 PM, "large data" <[email protected]> wrote: >I have an HTable instance instantiated as part of a singleton service. >This >singleton service is called from different threads from different parts of >the app. Reading through the HTable docs suggests not to use single HTable >instance for updates, if it's true how can incrementColumnValue provide >thread safety? > >thanks
