hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HBASE-1949) KeyValue expiration by Time-to-Live during major compaction is broken
Date Mon, 02 Nov 2009 22:04:59 GMT

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

Gary Helmling updated HBASE-1949:
---------------------------------

    Attachment: HBASE-1949-trunk.patch

Same patch for ScanQueryMatcher.match() return value and extra unit test, applied against
current trunk.

> KeyValue expiration by Time-to-Live during major compaction is broken
> ---------------------------------------------------------------------
>
>                 Key: HBASE-1949
>                 URL: https://issues.apache.org/jira/browse/HBASE-1949
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: regionserver
>    Affects Versions: 0.20.1
>            Reporter: Gary Helmling
>         Attachments: HBASE-1949-trunk.patch, ttl_expire-0.20.patch
>
>
> During a major compaction on a region in a column family with a configured TTL, it looks
like all KeyValues in a row after the first expired KeyValue are skipping and thrown out of
the newly written file (regardless of whether the would have been expired or not).
> The StoreScanner is skipping to the next row, even when other columns with a non-expirable
timestamp exists.  Unless I'm misunderstanding it, it seems like it should just seek to the
next column instead.  I discovered this when altering a table to lower the TTL for a column
family and force the expiration of some data which led to the entire row being expired in
some instances.

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


Mime
View raw message