hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jesse Yates (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-8702) Make WALEditCodec pluggable
Date Wed, 12 Jun 2013 20:34:20 GMT

     [ https://issues.apache.org/jira/browse/HBASE-8702?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jesse Yates updated HBASE-8702:
-------------------------------

    Attachment: hbase-8702-0.94-v1.patch

Updated patch for 0.94. Not significantly different from the other one, just a little nit
cleanup.

I didn't end up using ReflectionUtils since we don't have the HBase version in 0.94 and the
stuff from Hadoop looks a bit too heavy weight - sooo its back to a nullary constructor (which
you get by default anyways) and an empty init method. 

In the end, this ends up being just as easy for users to implement a WALEditCodec.

I'd like to commit tonight (assuming the tests for this pass locally).
                
> 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

Mime
View raw message