Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Message-ID: <33272228.4741275930712544.JavaMail.jira@thor>
Date: Mon, 7 Jun 2010 13:11:52 -0400 (EDT)
From: "Michele Catasta (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Subject: [jira] Updated: (HBASE-2681) Graceful fallback to NONE when the
 native compression algo is not found
In-Reply-To: <33258942.4701275930465823.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HBASE-2681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michele Catasta updated HBASE-2681:
-----------------------------------

    Attachment: HBASE-2681.patch

Extracted a method that tries to instantiate a native codec and, if not found, just writes a WARN in the logs instead of throwing a RuntimeException. Trivial test included.

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