[
https://issues.apache.org/jira/browse/HBASE-4608?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13226532#comment-13226532
]
stack commented on HBASE-4608:
------------------------------
bq. The above method allows to start computation at specified offset while
existing hashCode() doesn't have this parameter.
Should have at least the same name as the other two methods that do same (pity
WritableComparator.hashBytes w/ start offset doesn't exist).
bq. Looking at SequenceFile.Sorter.cloneFileAttributes(), I don't see a
convenient way for doing above.
When you create a write on a sequencefile, you can pass metadata:
http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/io/SequenceFile.Metadata.html
bq. For HLogKey, can we designate version of -2 for representing compressed
HLogKey ? If HLogKey isn't compressed, we write -1.
I don't know what this is in response to.
What about my other items?
> HLog Compression
> ----------------
>
> Key: HBASE-4608
> URL: https://issues.apache.org/jira/browse/HBASE-4608
> Project: HBase
> Issue Type: New Feature
> Reporter: Li Pi
> Assignee: Li Pi
> Fix For: 0.94.0
>
> Attachments: 4608-v19.txt, 4608v1.txt, 4608v13.txt, 4608v13.txt,
> 4608v14.txt, 4608v15.txt, 4608v16.txt, 4608v17.txt, 4608v18.txt, 4608v5.txt,
> 4608v6.txt, 4608v7.txt, 4608v8fixed.txt
>
>
> The current bottleneck to HBase write speed is replicating the WAL appends
> across different datanodes. We can speed up this process by compressing the
> HLog. Current plan involves using a dictionary to compress table name, region
> id, cf name, and possibly other bits of repeated data. Also, HLog format may
> be changed in other ways to produce a smaller HLog.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
