[
https://issues.apache.org/jira/browse/HBASE-4054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13059420#comment-13059420
]
Daniel Iancu commented on HBASE-4054:
-------------------------------------
@Stack, I've created a new patch where changes are pushed into HTablePool. I've
updated the unit test and added some more tests
@Ted putTable now checks the returned table to be a valid table.
tableFactory.releaseHTableInterface(table) will never return the table in pool.
I've added more comments in the code to describe better how it works
If any changes are required just let me know
> 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,
> HBASE-4054_Usability_improvement_to_HTablePool1.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
