hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrey Stepachev <oct...@gmail.com>
Subject Re: composite value vs composite qualifier
Date Tue, 22 Jun 2010 03:50:37 GMT
2010/6/22 Jonathan Gray <jgray@facebook.com>

> One minor correction to Andrey's thoughts...
>
> All updates to a given row are atomic.  Two operations from two different
> clients against the same row will always be done serially (updates to
> multiple columns will not be interleaved, one request will go and then the
> other will go... there is row-level locking).  If you are doing a
> read/modify/write operation, then this is different and to get atomicity
> there you would need to use something like checkAndPut.
>

Sorry for not clean description about what I mean. I mean, that in case of
serialisation you can't update different column simulateously from different
client (because you should serialize object as a whole). With different
columns - you can.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message