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-8636) Backport KeyValue Codec to 0.94 (HBASE-7413)
Date Wed, 05 Jun 2013 01:31:20 GMT

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

Jesse Yates updated HBASE-8636:

    Attachment: HBASE-8636-0.94-v4.patch

Updating diff for an issue Ted found - TestMultiSlaveReplication was failing. Turns out, it
was because we are still using the Writable serialization for the WALReplication.

I ended up just doing the easy hack of just using the WALEditCodec codec (without compression)
as the default codec when using Writable#readFields from the nullary constructor. This works
with the current mechanism of replication since it also enforces non-compression based serialization.

This does mean that we won't be able to do custom serialization over the wire. However, this
issue was all about doing serialization to the HLog anyways, so this isn't really a problem
(though certainly a caveat).

Still planning to commit tomorrow (though the latest patch).
> Backport KeyValue Codec to 0.94 (HBASE-7413)
> --------------------------------------------
>                 Key: HBASE-8636
>                 URL: https://issues.apache.org/jira/browse/HBASE-8636
>             Project: HBase
>          Issue Type: Improvement
>          Components: wal
>    Affects Versions: 0.94.9
>            Reporter: Jesse Yates
>            Assignee: Jesse Yates
>            Priority: Minor
>             Fix For: 0.94.9
>         Attachments: HBASE-8636-0.94.patch, HBASE-8636-0.94-v2.patch, HBASE-8636-0.94-v3.patch,
> Backport the KeyValueCodec/WALEditCodec stuff from trunk to 0.94 to support a more pluggable
KeyValue serialization. This doesn't include all the Cell code added to trunk, but rather
just providing a small layer of indirection for the serialization of a KeyValue in the WAL.

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

View raw message