Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@hbase.apache.org
Date: Thu, 8 Jan 2015 09:30:35 +0000 (UTC)
From: "Cosmin Lehene (JIRA)" <jira@apache.org>
To: dev@hbase.apache.org
Message-ID: <JIRA.12618672.1354585348000.36498.1420709435215@Atlassian.JIRA>
In-Reply-To: <JIRA.12618672.1354585348000@Atlassian.JIRA>
References: <JIRA.12618672.1354585348000@Atlassian.JIRA>
 <JIRA.12618672.1354585348691@arcas>
Subject: [jira] [Resolved] (HBASE-7267) [89-fb] Only create the dummy hfile
 for the compaction if necessary.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Cosmin Lehene resolved HBASE-7267.
----------------------------------
    Resolution: Invalid

[~liyin] closing for now. Please update if necessary

> [89-fb] Only create the dummy hfile for the compaction if necessary.
> --------------------------------------------------------------------
>
>                 Key: HBASE-7267
>                 URL: https://issues.apache.org/jira/browse/HBASE-7267
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Liyin Tang
>
> In HBASE-6059, it introduced a new behavior that the compaction would create the HFileWriter no mater whether there is any key/value as the output or not. This new behavior actually is conflicts with HBASE-5199 (Delete out of TTL store files before compaction selection) so that compacting the expired hfiles would generate one more expired hfiles.
> Actually we only needs to create the dummy hfile IFF the maxSequenceID among the compaction candidates is equal to the maxSequenceID among all the on-disk hfiles. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)