hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ramkrishna vasudevan <ramkrishna.s.vasude...@gmail.com>
Subject Re: Unique Put ends up twice in HBase?
Date Mon, 04 Feb 2013 07:29:04 GMT
Hi
If the put is successful and stored to memstore then it should be a
successful put.
What type of exception did the Server throw?

Regards
Ram

On Mon, Feb 4, 2013 at 12:50 PM, Mesika, Asaf <asaf.mesika@gmail.com> wrote:

> Hi,
>
> 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 ?
>
>
> Thanks,
>
> Asaf
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message