Your only chance is to run a major compaction on your table - that will get rid
of the delete marker. Then you can re-add the Put with the same TS.
-- Lars
ps. Rereading my email below... At some point I will learn to proof-read my
emails before I send them full of grammatical errors.
-
As Lars mentioned, the row is not physically deleted. The way which
Hbase uses is to insert a cell called tombstone which is used to
mask the deleted value, but value is still there (if the deleted value
is in the same memstore with tombstone, it will be deleted in the
memstore, so you will not
Uhm... Not exactly Lars...
Just my $0.02 ...
While I don't disagree w Lars, I think the question you have to ask is why is
the time stamp important?
Is it an element of the data or is it an artifact?
This kind of gets in to your Schema design and taking short cuts. You may want
to instead
Thanks yonghu.
That is HBASE-4241.
One small point: The deleted rows are not deleted from the memstore, but rather
not included when the memstore is flushed to disk.
-- Lars
- Original Message -
From: yonghu yongyong...@gmail.com
To: user@hbase.apache.org; lars hofhansl
Rows (or rather cells/columns) are not actually deleted. Instead they are
marked for deletion by a delete marker. The deleted cells are collected during
the next major or minor comaction.
As long as the marker exist new Put (with thje same timestamp as the existing
Put will affected by the
