Okay. Will take a look. Thanks
On Wed, Oct 17, 2018 at 8:28 AM Josh Elser wrote:
> The methods that you are invoking assume that the Phoenix JDBC driver
> (the java class org.apache.phoenix.jdbc.PhoenixDriver) is in use. It's
> not, so you get this error.
>
> The Phoenix "thick" JDBC driver is
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 is accurate (as is the
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 -
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
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."
Hi,
We are on Phoenix 4.7, so pre-Atomic Upserts that were introduced in 4.9. I
am trying to determine if there is a way to achieve similar functionality
with UPSERT SELECTs.
However, having read the documentation I'm not clear on the isolation-level
that is used when UPSERT SELECTs are executed
