hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cole Skoviak <cole.skov...@gmail.com>
Subject HConnection/HConnectionManager utilization
Date Mon, 23 Jun 2014 18:26:57 GMT
Hello, I'm currently working on making the move to HBase
and running into an issue as I am moving off the deprecated HTablePool API.

With the old HTablePool API I was able to pass in an HTableInterfaceFactory
which gave the ability to wrap the returned HTables for instrumentation
purposes. With the new HConnectionManager API however, I am no longer able
to pass in an HTableInterfaceFactory. Digging through the HBase code I saw a
couple potential routes to continue to utilize instrumentation, all which
have been blocked by various design decisions. I think the most important
option to note is there seems to be an intention to allow the consumer to
pass their own HConnection implementation [1], however the public
HConnection interface has a method with a return type with package private
access (as noted in the comment above its declaration). 

I am wondering if this is just functionality that just hasn't been exposed
yet, and/or if there is some alternate workflow that I should be taking in
order to maintain this functionality.


View this message in context: http://apache-hbase.679495.n3.nabble.com/HConnection-HConnectionManager-utilization-tp4060673.html
Sent from the HBase User mailing list archive at Nabble.com.

View raw message