hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Daniel Cryans <jdcry...@apache.org>
Subject Re: column can be got but can not be mapped
Date Tue, 19 Jan 2010 02:36:02 GMT
The problem here is you deleted something in the future so everything
before that is also considered as being deleted. If you run a major
compaction over that table it will all be cleaned (or if you don't do
anything it will happen in less than 24 hours).

Bottom line, it's better to always stay in the same time frame or
weird stuff happens.


On Mon, Jan 18, 2010 at 6:32 PM, johnson hong
<hong.jincheng@goodhope.net> wrote:
> There are abount 2,000,000 rows in  HTable.
> I have deleted some rows(column value is wrong,so delete it) with timestamp
> in currentTime nanos,
> then,in another mapReduce,I put new rows(rowKey is same as above )  with
> timestamp in currentTime millis,
> all the new rows do live in HTable because I can get them by hbase shell,but
> the problem is :when I map this HTable again,they are never be scanned.
> --
> View this message in context: http://old.nabble.com/column-can-be-got-but-can-not-be-mapped-tp27220186p27220186.html
> Sent from the HBase User mailing list archive at Nabble.com.

View raw message