Re: Connection Pooling?

Caching is thread starting quest, but at the end i have the same question about connection FAQ > On 18 Oct 2018, at 21:06, Josh Elser wrote: > > Batyrshin, you asked about statement caching which is different than > connection pooling. > > @JMS, yes, the FAQ is accurate (

Re: Connection Pooling?

Haha ;) For once I was hoping for it to be outdated ;) Thanks for the very prompt confirmation! JMS Le jeu. 18 oct. 2018 à 14:06, Josh Elser a écrit : > Batyrshin, you asked about statement caching which is different than > connection pooling. > > @JMS, yes, the FAQ

Re: Connection Pooling?

Batyrshin, you asked about statement caching which is different than connection pooling. @JMS, yes, the FAQ is accurate (as is the majority of the rest of the documentation ;)) On 10/18/18 1:14 PM, Batyrshin Alexander wrote: I've already asked the same question in this thread - http

Re: Connection Pooling?

I've already asked the same question in this thread - http://apache-phoenix-user-list.1124778.n5.nabble.com/Statements-caching-td4674.html > On 18 Oct 2018, at 19:44, Jean-Marc Spaggiari wrote: > > Hi, > > Is this statement in the FAQ still valid? > > "If Phoenix Connections are reused, it

Connection Pooling?

Hi, Is this statement in the FAQ still valid? "If Phoenix Connections are reused, it is possible that the underlying HBase connection is not always left in a healthy state by the previous user. It is better to create new Phoenix Connections to ensure that you avoid any potential issues."

Re: Connection pooling in Phoenix ?

, Dmitry Goldenberg <dgoldenberg...@gmail.com> wrote: > Hi, > > Could someone provide an overview of connection pooling vis a vis Phoenix? > > 1. Does Phoenix do connection pooling under the covers? We currently just > create connections and then close them once we're d

Connection pooling in Phoenix ?

Hi, Could someone provide an overview of connection pooling vis a vis Phoenix? 1. Does Phoenix do connection pooling under the covers? We currently just create connections and then close them once we're done with a given request which doesn't seem to drastically curtail performance. However

Phoenix connection pooling in a multi-tenant environment‏

Phoenix is an embedded driver and it automatically manages connection pooling. In case of multi-tenancy, tenant-specific connections are created by specifying tenantId property in JDBC. Does phoenix still automatically handle connection pooling, if I create multiple connections each