[
https://issues.apache.org/jira/browse/HBASE-8702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13681900#comment-13681900
]
Hudson commented on HBASE-8702:
-------------------------------
Integrated in HBase-0.94-security #165 (See
[https://builds.apache.org/job/HBase-0.94-security/165/])
HBASE-8702: Make WALEditCodec pluggable (Revision 1492518)
Result = SUCCESS
jyates :
Files :
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogReader.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/SequenceFileLogWriter.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEdit.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/regionserver/wal/WALEditCodec.java
*
/hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/replication/regionserver/ReplicationHLogReaderManager.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/wal/FaultySequenceFileLogReader.java
*
/hbase/branches/0.94/src/test/java/org/apache/hadoop/hbase/regionserver/wal/TestCustomWALEditCodec.java
> Make WALEditCodec pluggable
> ---------------------------
>
> Key: HBASE-8702
> URL: https://issues.apache.org/jira/browse/HBASE-8702
> Project: HBase
> Issue Type: Improvement
> Components: Replication, wal
> Reporter: Jesse Yates
> Assignee: Jesse Yates
> Fix For: 0.98.0, 0.95.2, 0.94.9
>
> Attachments: hbase-8702-0.94-v0.patch, hbase-8702-0.94-v1.patch,
> hbase-8702-trunk-v0.patch, hbase-8702-trunk-v1.patch,
> hbase-8702-trunk-v2.patch
>
>
> WALEditCode needs to be pluggable to support alternative serialziation
> mechanisms.
> The open question here is whether to support the alternative codec when doing
> replication - both clusters would need the codec on the classpath, which has
> additional overhead and also will be a little bit complicated when making the
> WAL serialization backwards compatible in 0.94.
> This is the follow-up to HBASE-8636.
--
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
