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

Ted Yu commented on HBASE-4820:
-------------------------------

@Jimmy:
Please upload latest patch to review board.

https://builds.apache.org/job/PreCommit-HBASE-Build/367//testReport/ was 
incomplete. Please run log splitting related tests manually.

Let's see what Kannan has to say.
                
> Distributed log splitting coding enhancement to make it easier to understand, 
> no semantics change
> -------------------------------------------------------------------------------------------------
>
>                 Key: HBASE-4820
>                 URL: https://issues.apache.org/jira/browse/HBASE-4820
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>    Affects Versions: 0.94.0
>            Reporter: Jimmy Xiang
>            Assignee: Jimmy Xiang
>            Priority: Minor
>              Labels: newbie
>             Fix For: 0.94.0
>
>         Attachments: 
> 0001-HBASE-4820-Distributed-log-splitting-coding-enhancement-to-make----it-easier-to-understand,-no-semantics-change..patch,
>  
> 0001-HBASE-4820-Distributed-log-splitting-coding-enhancement-to-make----it-easier-to-understand,-no-semantics-change..patch,
>  0001-HBASE-4820-Minor-distributed-log-splitting-enhanceme.patch, 
> 0001-HBASE-4820-Minor-distributed-log-splitting-enhanceme.patch, 
> 0001-HBASE-4820-Minor-distributed-log-splitting-enhanceme_new.patch
>
>
> In reviewing distributed log splitting feature, we found some cosmetic 
> issues.  They make the code hard to understand.
> It will be great to fix them.  For this issue, there should be no semantic 
> change.

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