hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8152) Avoid creating empty reference file when splitkey is outside the key range of a store file
Date Fri, 29 Mar 2013 00:59:17 GMT

    [ https://issues.apache.org/jira/browse/HBASE-8152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13616924#comment-13616924
] 

Hudson commented on HBASE-8152:
-------------------------------

Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #467 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/467/])
    HBASE-8152 Avoid creating empty reference file when splitkey is outside the key range
of a store file (clockfly) (Revision 1462275)

     Result = FAILURE
tedyu : 
Files : 
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionFileSystem.java
* /hbase/trunk/hbase-server/src/test/java/org/apache/hadoop/hbase/regionserver/TestStoreFile.java

                
> Avoid creating empty reference file when splitkey is outside the key range of a store
file
> ------------------------------------------------------------------------------------------
>
>                 Key: HBASE-8152
>                 URL: https://issues.apache.org/jira/browse/HBASE-8152
>             Project: HBase
>          Issue Type: Improvement
>          Components: Filesystem Integration, HFile
>    Affects Versions: 0.94.5
>            Reporter: clockfly
>            Assignee: clockfly
>            Priority: Minor
>             Fix For: 0.95.0, 0.94.7
>
>         Attachments: 8152-0.96v2.patch, hbase-8152.0.94patch.v2, HBASE-8152-0.94v3.patch,
HBASE-8152-0.96v1.patch, hbase-8152.patch0.94
>
>
> When splitting a store file, if the split key is before the first key, or greater than
the last key, then only one reference file should be created.
> Currently, two reference file will be created.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message