Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <1718596214.1216672651807.JavaMail.jira@brutus>
Date: Mon, 21 Jul 2008 13:37:31 -0700 (PDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-720) clean up inconsistencies around
 deletes
In-Reply-To: <1730290822.1215039885084.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-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack resolved HBASE-720.
-------------------------

       Resolution: Fixed
    Fix Version/s: 0.2.0

Applied a few days ago.  Thanks for the patch Izaak.

> clean up inconsistencies around deletes
> ---------------------------------------
>
>                 Key: HBASE-720
>                 URL: https://issues.apache.org/jira/browse/HBASE-720
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Izaak Rubin
>             Fix For: 0.2.0
>
>         Attachments: hbase-720.patch
>
>
> Compaction clears all cells behind any found 'delete' cell.  This makes for an inconsistency in that before the compaction runs, you can do a get or scan on a timestamp older than the delete cell and get results.  Confusing.
> Either preserve all cells for all time (or until > MAX_VERSIONS or TTL) or else make it so presence of a delete cell in the future stops client fetching anything older (expensive).

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