You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "Bryan Duxbury (JIRA)" <ji...@apache.org> on 2008/02/05 02:21:07 UTC

[jira] Assigned: (HBASE-406) Remove HTable and HConnection close methods

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

Bryan Duxbury reassigned HBASE-406:
-----------------------------------

    Assignee: Bryan Duxbury

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