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

Hadoop QA commented on HBASE-5801:
----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12523861/hbase_5801_v2.patch
  against trunk revision .

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 3 new or modified tests.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/job/PreCommit-HBASE-Build/1615//console

This message is automatically generated.
                
> [hbck] Hbck should handle case where some regions have different HTD settings 
> in .regioninfo files  (0.90 specific)
> -------------------------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-5801
>                 URL: https://issues.apache.org/jira/browse/HBASE-5801
>             Project: HBase
>          Issue Type: Improvement
>          Components: hbck
>    Affects Versions: 0.90.7
>            Reporter: Jonathan Hsieh
>            Assignee: Jimmy Xiang
>         Attachments: hbase_5801_v2.patch
>
>
> Recently, we encountered a case where some regions in a table have different 
> HTableDescriptor settings serialized into HDFS their HRegionInfo .regioninfo 
> file.  hbck expects all HTDs within a table to be the same and currently 
> bails out in this situation.
> We need to either point out a proper set of actions for the user to execute 
> or automatically convert the region to a common HTD (likely the most common 
> on, or possibly the "first one".)
> Not sure if this requires reformatting data but may require closing and 
> restarting a region.
> This issue is hbase 0.90.x specific -- 0.92+ keep all table info in a single 
> .tableinfo file.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to