hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-4054) Usability improvement to HTablePool
Date Fri, 01 Jul 2011 21:29:28 GMT

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

stack commented on HBASE-4054:
------------------------------

@Daniel Can we not push your improvement back into HTablePool rather than make a new class?
 The getTable returns an HTableInterface.  Can't we change it so it gives out your pool+table
carrying class instead?  We could add deprecated to putTable with a note that its going private?

> Usability improvement to HTablePool
> -----------------------------------
>
>                 Key: HBASE-4054
>                 URL: https://issues.apache.org/jira/browse/HBASE-4054
>             Project: HBase
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.90.3
>            Reporter: Daniel Iancu
>            Priority: Minor
>         Attachments: HBASE-4054_Usability_improvement_to_HTablePool.patch
>
>
> To improve the usability of the HTablePool the implementation should not rely on the
user returning the connection to the pool but rather do that transparently when user closes
the HTableImplementation it got.
>  
> To do that a HTableImplementation proxy implementation should be returned that wraps
a HTable object and holds a reference to the pool. When the client close the proxy it will
actually automatically return the wrapped HTable back in pool to be reused. In this case the
method HTablePool.putTable don't need to be public

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message