hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Dimiduk (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-9878) AbstractHBaseTool swallows exceptions
Date Fri, 06 Dec 2013 18:41:35 GMT

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

Nick Dimiduk updated HBASE-9878:

    Resolution: Not A Problem
        Status: Resolved  (was: Patch Available)

I'm changing my mind on this change. It's no a big deal for a developer to hack up the execution
path locally if they want to leave exceptions uncaught. I might change it back if jvm exit
codes prove consistent across implementations.

> AbstractHBaseTool swallows exceptions
> -------------------------------------
>                 Key: HBASE-9878
>                 URL: https://issues.apache.org/jira/browse/HBASE-9878
>             Project: HBase
>          Issue Type: Improvement
>          Components: util
>            Reporter: Nick Dimiduk
>            Assignee: Nick Dimiduk
>            Priority: Minor
>         Attachments: HBASE-9878.00.patch, HBASE-9878.01.patch, HBASE-9878.01.patch, HBASE-9878.01.patch
> AbstractHBaseTool catches any uncaught exceptions, logs them, and explicitly exists.
I believe the reason for this is to explicitly set a non-0 exit code for the process. However,
this means one cannot attach a debugger and break on uncaught exceptions.

This message was sent by Atlassian JIRA

View raw message