Return-Path: X-Original-To: apmail-hbase-issues-archive@www.apache.org Delivered-To: apmail-hbase-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4AD7ACEAC for ; Fri, 21 Jun 2013 18:50:21 +0000 (UTC) Received: (qmail 88012 invoked by uid 500); 21 Jun 2013 18:50:21 -0000 Delivered-To: apmail-hbase-issues-archive@hbase.apache.org Received: (qmail 87985 invoked by uid 500); 21 Jun 2013 18:50:21 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 87976 invoked by uid 99); 21 Jun 2013 18:50:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Jun 2013 18:50:21 +0000 Date: Fri, 21 Jun 2013 18:50:21 +0000 (UTC) From: "Lars Hofhansl (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-8721) Deletes can mask puts that happen after the delete MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/HBASE-8721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13690588#comment-13690588 ] Lars Hofhansl commented on HBASE-8721: -------------------------------------- But of course we can leave this issue open to indicate that we're still discussing this. > Deletes can mask puts that happen after the delete > -------------------------------------------------- > > Key: HBASE-8721 > URL: https://issues.apache.org/jira/browse/HBASE-8721 > Project: HBase > Issue Type: Improvement > Components: regionserver > Reporter: Feng Honghua > Attachments: HBASE-8721-0.94-V0.patch > > > this fix aims for bug mentioned in http://hbase.apache.org/book.html 5.8.2.1: > "Deletes mask puts, even puts that happened after the delete was entered. Remember that a delete writes a tombstone, which only disappears after then next major compaction has run. Suppose you do a delete of everything <= T. After this you do a new put with a timestamp <= T. This put, even if it happened after the delete, will be masked by the delete tombstone. Performing the put will not fail, but when you do a get you will notice the put did have no effect. It will start working again after the major compaction has run. These issues should not be a problem if you use always-increasing versions for new puts to a row. But they can occur even if you do not care about time: just do delete and put immediately after each other, and there is some chance they happen within the same millisecond." -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira