-Re: Unique Put ends up twice in HBase?
ramkrishna vasudevan 2013-02-04, 07:29
If the put is successful and stored to memstore then it should be a
What type of exception did the Server throw?
On Mon, Feb 4, 2013 at 12:50 PM, Mesika, Asaf <[EMAIL PROTECTED]> wrote:
> Can the following scenario occur?
> Create a Put for (rk1, cf1, cq1, value=1L)
> run hTable.batch
> Inside implementation:
> Put is sent to server
> Server throws an exception, but Put still is saved (WAL, memstore)
> Flush kicks in
> Client attempts a retry and succeeds, thus same put is written for the
> second time with different timestamp
> Fetching the data, assuming we allow maxVersion=2, we get value = 2 for
> that rk1, cf1, cq1 ?