[ https://issues.apache.org/jira/browse/HBASE-4820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13154385#comment-13154385 ]
Kannan Muthukkaruppan commented on HBASE-4820: ---------------------------------------------- This type of code factoring changes will make it harder for 89-fb/our internal branch changes to stay in sync with trunk; and to push/pull patches between the two revs. But agree that that can't be the reason to block all code factor/improvements. So those have to be evaluated on a case to case basis. Do we think these changes and code moves are worth it? [I have only looked at the specific changes superficially, but wanted to express the concern at least so that someone who has reviewed in detail can comment if this change is a must.] > 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 > > > 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