hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stack <st...@duboce.net>
Subject Re: HTablePool question
Date Tue, 14 Jul 2009 03:36:09 GMT
I'm an ex-user.  Commons pool is great.  IMO, it may be overkill in this
case.  You make the call Ken.

Thanks,
St.Ack

On Mon, Jul 13, 2009 at 6:02 PM, Ken Weiner <ken@gumgum.com> wrote:

> I guess the main advantage would be that the interface
>
> http://commons.apache.org/pool/apidocs/org/apache/commons/pool/ObjectPool.htmlis
> simple and well-understood by a lot of people, and also
>
> http://commons.apache.org/pool/apidocs/org/apache/commons/pool/impl/GenericObjectPool.htmlmakes
> a lot of things configurable and allows a built-in way to optionally
> verify that each HTable is working before handing it out.  If you think it
> is overkill to have more pooling functionality, than I'll stick to making
> simple modifications to the current tiny class.  I just thought that
> Commons
> Pool was a good fit for this functionality in HBase.
>
> On Mon, Jul 13, 2009 at 5:34 PM, Erik Holstad <erikholstad@gmail.com>
> wrote:
>
> > Hi Ken!
> > I don't think that the person that wrote the code for the pooler looked
> at
> > the code you mentioned.
> > I looked at it and it looked pretty good, but what would the advantage of
> > using that interface with it's
> > packages be instead of just using the tiny class we have now?
> >
> > Regards Erik
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message