You don't have to create a new Connection every time, but it is not
directly harmful to do so. This recommendation only goes one way (just
because you can create new connections each time, doesn't imply that you
have to, nor necessarily want to).
I wouldn't be worried about any sort of "healthy state". In the absence
of bugs, you would have to intentionally try very hard to muck up the
state of an HBase Connection.
On 8/15/18 6:07 PM, Batyrshin Alexander wrote:
https://phoenix.apache.org/faq.html#Should_I_pool_Phoenix_JDBC_Connections
If we should recreate connection every time then statements caching
looks useless.
Could you, please, explain in details what does it means "it is possible
that the underlying HBase connection is not always left in a healthy
state by the previous user"?
On 28 Jul 2018, at 06:09, James Taylor <jamestay...@apache.org
<mailto:jamestay...@apache.org>> wrote:
There's no statement caching available in Phoenix. That would be a
good contribution, though.
Thanks,
James
On Thu, Jul 26, 2018 at 10:45 AM, Batyrshin Alexander
<0x62...@gmail.com <mailto:0x62...@gmail.com>> wrote:
Hi all,
Im wondering how to enable statement caching in Phoenix JDBC Driver.
Is there anything like "cachePrepStmts"?
