You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Lars Hofhansl (JIRA)" <ji...@apache.org> on 2012/07/30 23:33:34 UTC
[jira] [Commented] (HBASE-6474) Separate exception types for
recoverable and non-recoverable errors
[ https://issues.apache.org/jira/browse/HBASE-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13425264#comment-13425264 ]
Lars Hofhansl commented on HBASE-6474:
--------------------------------------
There are beginnings of this in the form of subclasses of IOException. For example unrecoverable actions throws back a subclass of DoNotRetryException to a client.
> Separate exception types for recoverable and non-recoverable errors
> --------------------------------------------------------------------
>
> Key: HBASE-6474
> URL: https://issues.apache.org/jira/browse/HBASE-6474
> Project: HBase
> Issue Type: Improvement
> Components: client
> Reporter: Eli Collins
>
> While reading [about asynchbase|http://www.quora.com/HBase/What-are-the-best-HBase-client-libraries-in-each-language?srid=hqw] I noticed that HBase turns exposes all errors to clients as IOEs rather than use the exception hierarchy to separate recoverable and non-recoverable exceptions.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira