hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jim Kellerman (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-712) midKey found compacting is the first, not necessarily the optimal
Date Wed, 02 Jul 2008 22:16:45 GMT

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

Jim Kellerman resolved HBASE-712.
---------------------------------

    Resolution: Fixed

Hstore now returns the size of the store along with the midKey so HRegion can decide which
is the optimal mid key

> 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.


Mime
View raw message