[
https://issues.apache.org/jira/browse/HBASE-15881?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15314629#comment-15314629
]
Josh Elser commented on HBASE-15881:
------------------------------------
bq. If the patch gives some value and is very small, self-contained and not
risky, I personally would not hesitate to commit it to release branch even if
doesn't formally comply with the definition of bug fix. Me might have a wording
in the guideline saying that backporting of small backword-compatibly patches
is at the discretion of RM?
Yet again, moving farther and farther away from semver...
Kudus to Nick to playing hardball here. Compatibility statements must be strict
like this for a reason. Take a hypothetical:
1. User upgrades from 1.1.x to 1.1.y (with the BZIP compression only in 1.1.y).
2. User enables BZIP2 compression on a table
3. <time passes>
4. User finds super-critical bug, needs to revert to 1.1.x
You just screwed over that user now because the table with BZIP2 compression
won't work on 1.1.x. This should really not land in any active 1.x maintenance
line.
> Allow BZIP2 compression
> -----------------------
>
> Key: HBASE-15881
> URL: https://issues.apache.org/jira/browse/HBASE-15881
> Project: HBase
> Issue Type: New Feature
> Components: HFile
> Reporter: Lars Hofhansl
> Assignee: Lars Hofhansl
> Fix For: 2.0.0, 1.0.4, 1.2.2, 0.98.20, 1.1.6, 1.3.1
>
> Attachments: 15881-0.98.txt
>
>
> BZIP2 is a very efficient compressor in terms of compression rate.
> Compression speed is very slow, de-compression is equivalent or faster than
> GZIP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
