Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <154553973.1214879025123.JavaMail.jira@brutus>
Date: Mon, 30 Jun 2008 19:23:45 -0700 (PDT)
From: "Jim Kellerman (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Assigned: (HBASE-712) midKey found compacting is the first,
 not necessarily the optimal
In-Reply-To: <1192730109.1214451645003.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-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jim Kellerman reassigned HBASE-712:
-----------------------------------

    Assignee: Jim Kellerman

> midKey found compacting is the first, not necessarily the optimal
> -----------------------------------------------------------------
>
>                 Key: HBASE-712
>                 URL: https://issues.apache.org/jira/browse/HBASE-712
>             Project: Hadoop HBase
>          Issue Type: Bug
>            Reporter: stack
>            Assignee: Jim Kellerman
>            Priority: Minor
>             Fix For: 0.2.0
>
>
> It does this in HRegion:
> {code}
>       for (HStore store: stores.values()) {
>         final byte [] key = store.compact(force);                                                                                  
>         if (key != null && midKey == null) {                                                                                       
>           midKey = key;                                                                                                            
>         }
>       }
> {code}
> If many families, then we can return a suboptimal midKey.
> Marking minor but including in 0.2 because (I think) the fix is trivial.

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