[
https://issues.apache.org/jira/browse/HBASE-2256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12859929#action_12859929
]
Kevin Peterson commented on HBASE-2256:
---------------------------------------
What if I could do something like this:
Put put1 = ...
HTable.put(put1);
Delete delete = new Delete(...).guaranteeAfter(put1);
HTable.delete(delete);
Put put2 = new Put(...).guaranteeAfter(delete);
HTable.put(put2)
It seems like the distributed case isn't a problem since it's so unlikely, but
the delete then put seems more plausible. We could set the timestamp to 1ms
after the delete if needed. The occasional write will get a timestamp a few ms
in the future, which doesn't seem that bad. I think this solves Clint's
requirement of seeing a correct view without explicitly messing with timestamps.
> 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.
