[
https://issues.apache.org/jira/browse/HBASE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876413#action_12876413
]
Dave Latham commented on HBASE-2681:
------------------------------------
I agree it's not easy as it is right now.
Would it make sense to have a set of expected, "supported" compression schemes
in the settings. On regionserver startup, they check to see if the supported
algorithms are available, possibly report that to master or just fail to load.
Then when creating / altering a table immediately complain if the compression
isn't in the supported set?
> Graceful fallback to NONE when the native compression algo is not found
> -----------------------------------------------------------------------
>
> Key: HBASE-2681
> URL: https://issues.apache.org/jira/browse/HBASE-2681
> Project: HBase
> Issue Type: Improvement
> Components: io
> Reporter: Michele Catasta
> Priority: Minor
> Fix For: 0.21.0
>
> Attachments: HBASE-2681.patch
>
>
> stack's word: "Fellas have complained about the way broke lzo manifests
> itself. HBase will actually take on writes. Its only when it goes to flush
> that it drops the edits and in a way that is essentially hidden to the client
> - exceptions are thrown in the regionserver log. So, i'd say, make another
> issue if you don't mind but its not for you to fix, not unless you are
> inclined. It'd be about better user experience around choosing a compression
> that is not supported or not properly installed."
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
