[
https://issues.apache.org/jira/browse/HBASE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stack resolved HBASE-6341.
--------------------------
Resolution: Fixed
Fix Version/s: 0.94.1
0.92.2
Hadoop Flags: Reviewed
Committed 0.92, 0.94 and trunk. Thanks for the patch Micah.
> Publicly expose HConnectionKey
> ------------------------------
>
> Key: HBASE-6341
> URL: https://issues.apache.org/jira/browse/HBASE-6341
> Project: HBase
> Issue Type: Improvement
> Components: client
> Affects Versions: 0.92.0
> Reporter: Micah Whitacre
> Priority: Trivial
> Fix For: 0.92.2, 0.94.1
>
> Attachments: hbase_6341.patch
>
>
> HBASE-3777 introduced the concept of a HConnectionKey to quickly identify and
> compare Configuration instances which lack equals/hashCode values.
> We currently have use cases where being able to key Configuration objects in
> a similar way would be helpful. An example of this would be maintain a cache
> of HTablePool instances based on the HConnectionKey instead of the
> Configuration instance.
> I propose that HConnectionKey be made publicly available instead of its
> current package scope. Or another possibility would be to move it from being
> a static inner class to being part of the API.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
