hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Rawson <ryano...@gmail.com>
Subject Re: why not obtain row lock when geting a row
Date Mon, 28 Mar 2011 06:56:54 GMT
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 <wjiangwen@gmail.com> wrote:
> 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 28, 2011 at 1:45 PM, Ryan Rawson <ryanobjc@gmail.com> wrote:
>
>> Row locks are not necessary when reading. this changed, that is why that is
>> still there.
>> On Mar 27, 2011 10:42 PM, "jiangwen w" <wjiangwen@gmail.com> wrote:
>> > I think a row lock should be obtained before getting a row.
>> > but the following method in HRegion class show a row lock won't be
>> obtained
>> >
>> > *public Result get(final Get get, final Integer lockid)*
>> > *
>> > *
>> > although there is a* lockid* parameter, but it is not used in this
>> method.
>> >
>> > Sincerely
>> > Vince Wei
>>
>

Mime
View raw message