[ https://issues.apache.org/jira/browse/HBASE-6341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408334#comment-13408334 ]
stack commented on HBASE-6341: ------------------------------ @Micah Tell us more about your need. This is ugly internals. We already let out way too much of our dirty laundry. For sure you need these dirty bloomers exposed? > 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 > 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