Sure, the use case is updating 100s of rows [each row has to be updated atomically] by multiple threads. Batching is setup to do aggregate data on a regionserver granularity. The objective is to reduce the rpc overhead similar to batch get or batch put. The objective is NOT to do cross-row locking or expect any type of multi-row atomicity.
hari On Mon, Apr 29, 2013 at 9:13 AM, Ted Yu <[email protected]> wrote: > checkAndPut() checks specific row. Can you outline your requirement in a > bit more detail ? > > Meaning, if you supply List of Puts to the batch API. Are the Puts > targeting the same row ? If not, how would the Puts outside the region > where the checked row belongs be handled ? > > Cheers > > On Mon, Apr 29, 2013 at 8:30 AM, Hari Mankude <[email protected] > >wrote: > > > Is there a batch version of checkAndPut() in the trunk? If so, can you > > point me to the appropriate jira? > > > > thanks > > hari > > >
