hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-2055) Serialize WAL as Avro records
Date Mon, 12 May 2014 00:45:16 GMT

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

Andrew Purtell resolved HBASE-2055.

    Resolution: Invalid

Not going to happen

> Serialize WAL as Avro records
> -----------------------------
>                 Key: HBASE-2055
>                 URL: https://issues.apache.org/jira/browse/HBASE-2055
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Andrew Purtell
>            Priority: Minor
>         Attachments: HBASE-2055-v2.patch, HBASE-2055-v3.patch, HBASE-2055-v4.patch, HBASE-2055.patch,
TEST-org.apache.hadoop.hbase.TestFullLogReconstruction.txt.gz, TEST-org.apache.hadoop.hbase.regionserver.wal.TestHLog.txt.gz,
TEST-org.apache.hadoop.hbase.regionserver.wal.TestLogRolling.txt.gz, jackson-core-asl-1.0.1.jar,
jackson-mapper-asl-1.0.1.jar, paranamer-1.5.jar, test-site.patch
> There was some advocacy of using Avro for serialization of HBase WAL records up on hbase-dev@.
Idea is Hadoop core is getting away from Writables and Avro is the blessed replacement. 
> I think we have this criteria for its use:
> 1) Performance of writing Avro records is no worse than that for writing Writables into
a SequenceFile.
> 2) Space consumed by Avro serialization is no worse than that of Writables
> 3) File format is amenable to appends (cannot require valid trailers, etc.)
> I'll put up a patch so we can try it out. 

This message was sent by Atlassian JIRA

View raw message