[
https://issues.apache.org/jira/browse/HBASE-10434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13885915#comment-13885915
]
Jeffrey Zhong commented on HBASE-10434:
---------------------------------------
[~anoopsamjohn] I saw your changed CompressionContext constructor. Though we
mark it as Private, Phoenix is using it. The similar thing also happened for
Phoenix as well on KeyValue on earlier changes. Thanks.
> Store Tag compression information for a WAL in its header
> ---------------------------------------------------------
>
> Key: HBASE-10434
> URL: https://issues.apache.org/jira/browse/HBASE-10434
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.98.0
> Reporter: Anoop Sam John
> Assignee: Anoop Sam John
> Fix For: 0.98.0, 0.99.0
>
> Attachments: HBASE-10434.patch
>
>
> We can enable/disable tag compression along with WAL compression using the
> config,
> hbase.regionserver.wal.tags.enablecompression -> Defaults to true so that
> compress tags when WAL compress is ON.
> We are not storing this info abt whether a WAL containing compressed tags or
> not in the WAL header and use that in the read path. So dynamic change of
> this in some servers may cause issue when an RS having this value as true
> have to read and split a WAL generated from n RS where this value was false.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
