Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <31648592.791271380405047.JavaMail.jira@thor>
Date: Thu, 15 Apr 2010 21:13:25 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Resolved: (HBASE-2453) Revisit compaction policies after
 HBASE-2248 commit
In-Reply-To: <13826409.151411271366450620.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

stack resolved HBASE-2453.
--------------------------

    Hadoop Flags: [Reviewed]
        Assignee: Jonathan Gray
      Resolution: Fixed

Applied to 0.20.4 and 0.20.4 and trunk.  Made HBASE-2454 for major compaction delete issue.  Thanks for patch Jon.

> Revisit compaction policies after HBASE-2248 commit
> ---------------------------------------------------
>
>                 Key: HBASE-2453
>                 URL: https://issues.apache.org/jira/browse/HBASE-2453
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: Jonathan Gray
>            Assignee: Jonathan Gray
>            Priority: Critical
>             Fix For: 0.20.4, 0.20.5, 0.21.0
>
>         Attachments: HBASE-2453-v1.patch
>
>
> HBASE-2248 turned Gets into Scans server-side.  It also removed the invariant that deletes in a file only apply to other files and not itself (no longer processes MemStore deletes when the delete happens).  This has implications for our minor compaction policy.
> We are currently processing deletes during minor compactions in a way that makes it so we do the actual deleting as we compact, but we retain the delete records themselves.  This makes it so we retain the invariant of deletes only applying to other files.
> Since this is now gone post HBASE-2248, we should revisit our compaction policies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira