so client may read dirty data, considering the following case
client#1 update firstName and lastName for a user.
client#2 read the information of the user when client#1 updated firstName
and will update lastName.
so client#1 read the latest firstName, but the old lastName.
Sincerely
On Mon, Mar
That is not the case, please see:
https://issues.apache.org/jira/browse/HBASE-2248
There are alternative mechanisms (outlined in that JIRA) to assure
atomic row reads.
-ryan
On Sun, Mar 27, 2011 at 11:54 PM, jiangwen w wjiang...@gmail.com wrote:
so client may read dirty data, considering the
This isn't Iron Chef American Idol All Stars HBase Edition, showing
that you can actually provide some form of answer is already a #win by
itself.
J-D
On Mon, Mar 28, 2011 at 9:52 AM, Weishung Chung weish...@gmail.com wrote:
Thank you Jean for the reading materials, I've been reading the
Resending Ted's vote. He got a failure trying to post the list.
-- Forwarded message --
From: Ted Yu yuzhih...@gmail.com
Date: Mon, Mar 28, 2011 at 10:27 AM
Subject: Re: ANN: hbase 0.90.2 Release Candidate 0 available for download
To: dev@hbase.apache.org
Cc: Stack
