On Mon, Mar 19, 2012 at 11:44 AM, Maysam Yabandeh wrote:
> hbase-trx, on the other hand, does not provide read snapshots and is not safe
> with client failures.
hbase-trx, https://github.com/hbase-trx/hbase-transactional-tableindexed,
has not been updated in over a year.
St.Ack
Deepika,
It is up to you to decide the granularity of transactions, whether at the
reduce level or at the M/R job level. Your application just need to be able to
(efficiently) rerun the transaction in case of an abort. The transaction
feature provides your application with two good properties:
inal Message-
>> From: Maysam Yabandeh [mailto:may...@yahoo-inc.com]
>> Sent: Monday, March 19, 2012 11:45
>> To: user@hbase.apache.org
>> Subject: Re: Hbase Transactional support
>>
>> Hi Deepika,
>>
>> Omid provides Snapshot Isolation (SI), wh
Thanks Maysam. I am trying out Omid to see if it will fit my needs.
As I told you I am writing to hbase from a map reduce jobs. If my commit
and rollback is around a reducer task then it will be quite straight
forward. But if the commit should happen if all tasks of the M/R job
succeed(which is wh
t level of isolation?
Apologies if this is clear in the code, which I haven't yet read thoroughly.
Thanks,
Sandy
> -Original Message-
> From: Maysam Yabandeh [mailto:may...@yahoo-inc.com]
> Sent: Monday, March 19, 2012 11:45
> To: user@hbase.apache.org
> Subject: Re: Hba
Hi Deepika,
Omid provides Snapshot Isolation (SI), which is a well-known isolation
guarantee in database systems such as Oracle. In short, each transaction reads
from a consistent snapshot that does not include partial changes by concurrent
(or failed) transactions. SI also prevents write-write
