Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-6474

Separate exception types for recoverable and non-recoverable errors

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Client
    • Labels:
      None

      Description

      While reading about asynchbase 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.

        Issue Links

          Activity

          Hide
          eli Eli Collins added a comment -

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

          Show
          eli Eli Collins added a comment - 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).
          Hide
          lhofhansl Lars Hofhansl added a comment -

          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.

          Show
          lhofhansl Lars Hofhansl added a comment - 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.

            People

            • Assignee:
              Unassigned
              Reporter:
              eli Eli Collins
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:

                Development