Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 ronsher@gmail.com does not designate 216.139.236.26 as permitted sender)
Date: Wed, 19 Feb 2014 23:19:26 -0800 (PST)
From: Ron Sher <ronsher@gmail.com>
To: user@hbase.apache.org
Message-ID: <1392880766735-4056189.post@n3.nabble.com>
In-Reply-To: 
 <CALte62zJDZ6RqvKiMBUrZeFkx=6Vd+z-nP+JmrrCS6eFhyncZQ@mail.gmail.com>
References: <1392814501378-4056162.post@n3.nabble.com>
 <CALte62zJDZ6RqvKiMBUrZeFkx=6Vd+z-nP+JmrrCS6eFhyncZQ@mail.gmail.com>
Subject: Re: Hbase shell - deletall doesnt remove records
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I work with Yaniv and we now have a better understanding of the issue.
It happens when you specifically set a timestamp that is a large long value.
For example 635265926417915010

If you then try to delete the whole line, without specifying the timestamp,
thinking that it will delete the whole line it simply doesn't work. You get
no errors, but when you later try to get that line - you get it back.

There is a constant repro:
Lets say we have a table called t1 with some CF content

put 't1', 'blah', 'content:document', '{}', 635265926417915010
get 't1', 'blah'
deleteall 't1', 'blah'
get 't1', 'blah'


--
View this message in context: http://apache-hbase.679495.n3.nabble.com/Hbase-shell-deletall-doesnt-remove-records-tp4056162p4056189.html
Sent from the HBase User mailing list archive at Nabble.com.