thanks all your resonses.
i think row lock has been implemented by MVCC in hbase at that release.
@Josh ,in MVCC there is a variable named 'memstoreWrite' to achieve
'across-transaction' isolation.for reads,the readers will not see the data
writen at T2(memstoreWrite) before the memstoreRead is
> since if i have 10 rows to update,then it means that 9 rows have no
> rowlocks.so is 'at least one rowlock' more symbolic than practical
> significane?
Pls note that it is doMiniBatchMutation. 10 rows there in ur batch.
The batch might get complete in many mini batches. When one mini
batch
Please be patient when waiting for a response. Apache HBase is made up
of community volunteers. Your expectation should be on the order of many
hours (although, we strive to be faster).
I'd recommend that you begin by looking at a newer release than 0.94.2
as there have likely been over 50
hi all,i dived into hbase source these days.when i read at the
HRegion#doMiniBatchMutation(...) block then one question flashed in my mind:why
did writer use at least one rowlock to implement mutation?(ie.Puts or Deletes
etc)
since if i have 10 rows to update,then it means that 9 rows have
