[
https://issues.apache.org/jira/browse/HBASE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12837947#action_12837947
]
Clint Morgan commented on HBASE-2256:
-------------------------------------
I have only noticed this in unit tests and a non-distributed setup. However,
this Delete,Put happens in ITHbase's IndexRegion which means that even in a
distributed setup the client for the put/delete and the regionserver handling
them could be in the same JVM.
For the put, put case, it seems to me this could be a real issue. Even in
distributed setup sequential puts could happen in the same ms no? However, I
did a similar test for Put after Put and it seems to always work. If it did
not, I'm sure users would have complained loudly by now.
>From my point of view, it would be nice to have this behavior for Put after
>Delete as well.
I'm not saying I need finer granularity tham ms. Just that when I'm never
explicitly messing with timestamps, I always see a "correct" view that reflects
my last operation. I just skimmed over the bigtable paper, and could not find
an explication about what they do in this case..
> Delete row, followed quickly to put of the same row will sometimes fail.
> ------------------------------------------------------------------------
>
> Key: HBASE-2256
> URL: https://issues.apache.org/jira/browse/HBASE-2256
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.3
> Reporter: Clint Morgan
> Attachments: hbase-2256.patch
>
>
> Doing a Delete of a whole row, followed immediately by a put to that row will
> sometimes miss a cell. Attached is a test to provoke the issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
