As I recall, I did try setting auto commit to True, but it did not help.
With/without auto commit, my writes would work soon after I started
SQuirreL Client, but always stopped working after some time passed until I
restarted the client.
I discovered I needed the extra jar when I had a complex
Correct, James:
Phoenix-4.7.0 uses Calcite-1.6.0. This included lots of goodies includes
commit/rollback support. Phoenix-4.6.0 used Calcite-1.3.0. In general,
if you want to use the QueryServer, I'd strongly recommend trying to go
with Phoenix-4.7.0. You'll inherit *lots* of
Steve,
For deletes and upsets through the query server in 4.6, did you set auto
commit to be true by default (set phoenix.connection.autoCommit to true)?
In 4.7 this has been fixed, but prior to this, I believe commit and
rollback were a noop. Is that right, Josh?
Thanks,
James
On Thursday, March
I forgot to mention, although the docs say only one jar is needed, I found
that I also had to have commons-collections-3.2.1.jar in the class path,
too.
On Thu, Mar 24, 2016 at 10:07 AM, Steve Terrell
wrote:
> Hi! Everything I say below pertains only to Phoenix 4.6.0.
Hi! Everything I say below pertains only to Phoenix 4.6.0. Don't know
what changes in 4.7.0.
Judging from the port number, you must be using the thin client server.
Have you seen this page? https://phoenix.apache.org/server.html . It has
JDBC info.
I got the thin client jar to work with
I am interested in building a Go client to query the phoenix query
server using protocol buffers.
The query server is running on http://localhost:8765, so I tried POSTing
to localhost:8765 with the marshalled protocol buffer as the body.
Unfortunately, the server responds with: