You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/03/21 17:59:29 UTC

[jira] Created: (HBASE-539) In general, close should not throw exception

In general, close should not throw exception
--------------------------------------------

                 Key: HBASE-539
                 URL: https://issues.apache.org/jira/browse/HBASE-539
             Project: Hadoop HBase
          Issue Type: Improvement
    Affects Versions: 0.16.0, 0.2.0, 0.1.0
            Reporter: stack


In particular, a close of a scanner whose lease has timed out elsewhere will throw an UnknownScannerException rather than just return.  Makes it so can't easily put the close into a finally on client side.

This issue is about reviewing all calls to close to make sure all don't throw exceptions gratutiously.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Assigned: (HBASE-539) In general, close should not throw exception

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury reassigned HBASE-539:
-----------------------------------

    Assignee: Bryan Duxbury

> In general, close should not throw exception
> --------------------------------------------
>
>                 Key: HBASE-539
>                 URL: https://issues.apache.org/jira/browse/HBASE-539
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.16.0, 0.2.0, 0.1.0
>            Reporter: stack
>            Assignee: Bryan Duxbury
>             Fix For: 0.2.0
>
>
> In particular, a close of a scanner whose lease has timed out elsewhere will throw an UnknownScannerException rather than just return.  Makes it so can't easily put the close into a finally on client side.
> This issue is about reviewing all calls to close to make sure all don't throw exceptions gratutiously.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Resolved: (HBASE-539) In general, close should not throw exception

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury resolved HBASE-539.
---------------------------------

    Resolution: Fixed

Committed as part of HBASE-521

> In general, close should not throw exception
> --------------------------------------------
>
>                 Key: HBASE-539
>                 URL: https://issues.apache.org/jira/browse/HBASE-539
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.16.0, 0.2.0, 0.1.0
>            Reporter: stack
>            Assignee: Bryan Duxbury
>             Fix For: 0.2.0
>
>
> In particular, a close of a scanner whose lease has timed out elsewhere will throw an UnknownScannerException rather than just return.  Makes it so can't easily put the close into a finally on client side.
> This issue is about reviewing all calls to close to make sure all don't throw exceptions gratutiously.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (HBASE-539) In general, close should not throw exception

Posted by "Bryan Duxbury (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Duxbury updated HBASE-539:
--------------------------------

    Fix Version/s: 0.2.0

> In general, close should not throw exception
> --------------------------------------------
>
>                 Key: HBASE-539
>                 URL: https://issues.apache.org/jira/browse/HBASE-539
>             Project: Hadoop HBase
>          Issue Type: Improvement
>    Affects Versions: 0.16.0, 0.2.0, 0.1.0
>            Reporter: stack
>             Fix For: 0.2.0
>
>
> In particular, a close of a scanner whose lease has timed out elsewhere will throw an UnknownScannerException rather than just return.  Makes it so can't easily put the close into a finally on client side.
> This issue is about reviewing all calls to close to make sure all don't throw exceptions gratutiously.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.