You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Dave Latham (JIRA)" <ji...@apache.org> on 2010/06/07 22:18:55 UTC

[jira] Commented: (HBASE-2681) Graceful fallback to NONE when the native compression algo is not found

    [ https://issues.apache.org/jira/browse/HBASE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876393#action_12876393 ] 

Dave Latham commented on HBASE-2681:
------------------------------------

It's definitely not good to fail silently at a later time.

However, I'd prefer to see it fail loudly and immediately if I try to use a form of compression that is not available rather than a quiet fallback to no compression that I would likely not notice.

> 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.