-Consistency issue when a Put is in the memstore but a more recent Delete is cleaned in a major compaction
I looked around a bit and couldn't find a jira directly related to
this. Here's an example of inconsistency in every HBase version
(although the shell won't let you do it in trunk):
create 't', 'f'
delete 't', '1', 'f:1', 3
put 't', '1', 'f:1', '1', 2
The first scan returns nothing, the second one returns the row 1. This
is the same when the delete is bulk loaded and then major compacted
(which is a more legitimate use case).
What's the common wisdom here? Does anyone remember if we had this
discussion in the past?