Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <23592265.90401280513549482.JavaMail.jira@thor>
Date: Fri, 30 Jul 2010 14:12:29 -0400 (EDT)
From: "stack (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-2792) Create a better way to chain log
 cleaners
In-Reply-To: <14273326.69391277509914037.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-2792?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-2792:
-------------------------

    Attachment: HBASE-2792.patch

DIff copied from review.hbase.org, the diff I'm about to commit.

> Create a better way to chain log cleaners
> -----------------------------------------
>
>                 Key: HBASE-2792
>                 URL: https://issues.apache.org/jira/browse/HBASE-2792
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>            Assignee: Li Chongxin
>             Fix For: 0.90.0
>
>         Attachments: HBASE-2792.patch
>
>
> From Stack's review of HBASE-2223:
> {quote}
> Why this implementation have to know about other implementations?  Can't we do a chain of decision classes? Any class can say no?  As soon as any decision class says no, we exit the chain.... So in this case, first on the chain would be the ttl decision... then would be this one... and third would be the snapshotting decision. You don't have to do the chain as part of this patch but please open an issue to implement.
> {quote}

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