[jira] Commented: (HBASE-2286) [Transactional Contrib] Correctly handle or avoid cases where writes occur in same millisecond

["George P. Stathis (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12852680#action_12852680 ] 

George P. Stathis commented on HBASE-2286:
------------------------------------------

Hi Clint. Regarding the note you left on the users list, I wanted to clarify something:

Does the remaining bug occur when an column gets deleted in the base table as opposed to the entire row? So, if I were indexing a given column:qualifier and wanted to delete the entire cell history, it would not get cleared from the index?

Tank you in advance.

On Mon, Mar 29, 2010 at 12:25 PM, Clint Morgan <cl...@troove.net> wrote:
NOTE: Current patch has a bug in it where if you delete only an
"additionalColumn" in the base table, then it does not get deleted in
the index. I'll put a fix for that up shortly.

> [Transactional Contrib] Correctly handle or avoid cases where writes occur in same millisecond
> ----------------------------------------------------------------------------------------------
>
>                 Key: HBASE-2286
>                 URL: https://issues.apache.org/jira/browse/HBASE-2286
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: contrib
>            Reporter: Clint Morgan
>             Fix For: 0.20.4, 0.21.0
>
>         Attachments: hbase-2286.patch
>
>
> This patch fixes a few issues where puts/deletes occur with the same timestamp.
> In the indexing layer, we avoid a Delete followed by a Put to the same row for the index update. When the row is the same, we can just do the put.
> In the transactional layer, we correctly handled put, put, scan. This way the scan will see the last put, even if they have the same timestamp.
> Remove the sleep to fix the putPutScan transactional test, and run it many times to be sure we hit the case where they are in the same millisecond.
> Also some small cleanup, null handling, and fail-fast changes.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.