hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrew Purtell <apurt...@apache.org>
Subject Re: hbase is not deleting the cell when a Put with a KeyValue, KeyValue.Type.Delete is submitted
Date Thu, 21 Aug 2014 20:16:24 GMT
See also the latest comment on the JIRA. :-)


On Thu, Aug 21, 2014 at 1:13 PM,
​​
Srikanth Srungarapu <srikanth235@gmail.com> wrote:

> Hi,
> Did you try taking a look at
>
> https://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/RowMutations.html
> ?
>
> Thanks,
> Srikanth.
>
>
> On Thu, Aug 21, 2014 at 1:03 PM, Armaselu, Cristian <carmaselu@epsilon.com
> >
> wrote:
>
> > Consider 2 JVM executing the following on the same row key
> > JVM1
> >
> >     (1) Put to update new "columns",
> >     (2) Delete to remove "column" X value (since incoming data is null
> for
> > column X)
> >
> > JVM2
> >
> >     (1) Put to update new "columns",
> >     (2) Delete to remove "column" Y value (since incoming data is null
> for
> > column X)
> >
> > What happens if the hbase API requests are applied in this order (since 2
> > JVM, 2 threads of execution)
> > JVM1 (1) Put
> > JVM2 (2) Delete
> > JVM1 dies
> > JVM2 (2) Delete
> > Or you can think of any other combination with 4 operations instead of 2
> >
> > The data is corrupted, none of the 2 new records were applied, we don't
> > have the previous record stored in hbase.
> >
> ​
> ​
> ​
> ​
>


-- 
Best regards,

   - Andy

Problems worthy of attack prove their worth by hitting back. - Piet Hein
(via Tom White)

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