hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-406) Remove HTable and HConnection close methods
Date Fri, 08 Feb 2008 19:47:07 GMT

    [ https://issues.apache.org/jira/browse/HBASE-406?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12567174#action_12567174

stack commented on HBASE-406:

+1 on patch but doesn't apply to TRUNK.

FYI, empty finally's would be better removed altogether.

> Remove HTable and HConnection close methods
> -------------------------------------------
>                 Key: HBASE-406
>                 URL: https://issues.apache.org/jira/browse/HBASE-406
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: client
>            Reporter: Bryan Duxbury
>            Assignee: Bryan Duxbury
>            Priority: Minor
>             Fix For: 0.2.0
>         Attachments: 406.patch
> As a holdover from the old style of full-meta caching, HTable and HConnection have close
methods that are intended to release resources when you are done using a table. However, with
the new lazy cache, it no longer makes sense to manually manage your connection cache. Instead,
we should remove HTable.close and HConnection.close and allow the cache's resource usage to
be managed by other means. 
> This will have the effect of making opening and "closing" HTables very cheap once they've
been opened at least once. This is actually sort of critical for applications like REST, which
use a lot of instances of HTable rather than caching a single HTable. Opening and closing
the table in the old style would be very expensive.

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

View raw message