You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Eli Collins (JIRA)" <ji...@apache.org> on 2012/07/30 18:13:35 UTC
[jira] [Created] (HBASE-6474) Separate exception types for
recoverable and non-recoverable errors
Eli Collins created HBASE-6474:
----------------------------------
Summary: 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
[jira] [Commented] (HBASE-6474) Separate exception types for
recoverable and non-recoverable errors
Posted by "Eli Collins (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6474?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426900#comment-13426900 ]
Eli Collins commented on HBASE-6474:
------------------------------------
Thanks, would be good to doc that (eg in javadoc and/or explicit class names eg UnrecoverableException) and articulate the remaining work (perhaps as sub-tasks of this jira if it's a lot).
> 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
[jira] [Commented] (HBASE-6474) Separate exception types for
recoverable and non-recoverable errors
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ 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