[
https://issues.apache.org/jira/browse/HBASE-8671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13674143#comment-13674143
]
Hudson commented on HBASE-8671:
-------------------------------
Integrated in HBase-0.94 #1004 (See
[https://builds.apache.org/job/HBase-0.94/1004/])
HBASE-8671: Per-region WAL breaks CP backwards compatibility in 0.94 for
non-enabled case (Revision 1489274)
Result = SUCCESS
jyates :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/RegionServerServices.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/util/MockRegionServerServices.java
> Per-region WAL breaks CP backwards compatibility in 0.94 for non-enabled case
> -----------------------------------------------------------------------------
>
> Key: HBASE-8671
> URL: https://issues.apache.org/jira/browse/HBASE-8671
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.9
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.94.9
>
> Attachments: hbase-8671-v0.patch
>
>
> Moving from a single WAL to the possibility of multiple WALs, the method
> signature in RegionServerServices became:
> {code}
> /** @return the HLog for a particular region. Pass null for getting the
> * default (common) WAL */
> public HLog getWAL(HRegionInfo regionInfo) throws IOException;
> {code}
> However, CPs that previously needed access to the WAL would just call:
> {code}
> RegionServerServices.getWAL();
> {code}
> Which is equivalent to calling:
> {code}
> RegionServerServices.getWAL(null);
> {code}
> but which requires a code change, recompilation, and possibly an additional
> compatibility layer for _different versions of 0.94_... not a great situation.
--
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
