hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "George P. Stathis (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-2286) [Transactional Contrib] Correctly handle or avoid cases where writes occur in same millisecond
Date Wed, 07 Apr 2010 21:23:07 GMT

     [ https://issues.apache.org/jira/browse/HBASE-2286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

George P. Stathis updated HBASE-2286:

    Attachment: hbase-2286-v2-trunk.patch

Verified hbase-2286-v2.patch on http://svn.apache.org/repos/asf/hadoop/hbase/branches/0.20
and all tests pass.

Ported hbase-2286-v2.patch to trunk (see attached) and verified that all maven tests pass
(core and contrib).

We'll need one of the committers to check this in. I talked to jdcryans on IRC this morning
and gave a heads up. I'll notify #hbase that this is ready.

> [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-v2-trunk.patch, hbase-2286-v2.patch, 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.

View raw message