[
https://issues.apache.org/jira/browse/HBASE-8702?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678284#comment-13678284
]
Jesse Yates commented on HBASE-8702:
------------------------------------
{quote}
As for the constant, usually its put in the main class
{quote}
Fair enough - I frequently find it hard to find constants if they are all over
the place. HConstants is a decent enough location, but I'm happy to put it in
the class too.
{quote}
Wrt custom KVs - this is only WAL though, right? What about HFile-s?
{quote}
I don't need it for HFiles, this is essentially about storing temporary
meta-data that just needs to be replayed under certain scenarios. But having
the KeyValueCodec/CellCodec there makes this completely possible to use with
HFiles, if someone wanted to... but that ship already sailed with HBASE-8636,
this just gives me a handle.
> 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-trunk-v0.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
