Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <102020314.1257448112576.JavaMail.jira@brutus>
Date: Thu, 5 Nov 2009 19:08:32 +0000 (UTC)
From: "Jonathan Gray (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Assigned: (HBASE-1949) KeyValue expiration by Time-to-Live
 during major compaction is broken
In-Reply-To: <1086954.1256941081072.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Gray reassigned HBASE-1949:
------------------------------------

    Assignee: Gary Helmling

> 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
>            Assignee: Gary Helmling
>             Fix For: 0.20.2, 0.21.0
>
>         Attachments: HBASE-1949-0.20.patch, HBASE-1949-trunk.patch, HBASE-1949-v2-0.20.patch, HBASE-1949-v2-trunk.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.