[
https://issues.apache.org/jira/browse/HBASE-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13061797#comment-13061797
]
Hudson commented on HBASE-4054:
-------------------------------
Integrated in HBase-TRUNK #2014 (See
[https://builds.apache.org/job/HBase-TRUNK/2014/])
HBASE-4054 extending HTable because HTableInterface does not include
getRegionInfos and setAutoFlush
tedyu :
Files :
* /hbase/trunk/src/main/java/org/apache/hadoop/hbase/client/HTablePool.java
> 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: 4054.addendum,
> HBASE-4054_Usability_improvement_to_HTablePool-trunk.patch,
> 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
