If you invoked a commit on PQS, it should have flushed any cached values
to HBase. The general messages you described in your initial post look
correct at a glance.
If you have an end-to-end example of this that I can play with, I can
help explain what's happening inside of PQS. If you want
@James Taylor:
I was unable to reproduce the problem today after extensive testing. I
think the problem is probably due to SquirrelSQL and not the query
server. Not familiar with the thin-client and SquirrelSQL, but does it
do any caching?
On 3/04/2016 5:12 AM, James Taylor wrote:
Glad you
Glad you have a work around. Would you mind filing a Calcite bug for the
Avatica component after you finish your testing?
Thanks,
James
On Sat, Apr 2, 2016 at 4:10 AM, F21 wrote:
> I was able to successfully commit a transaction if I set the serialization
> of the phoenix
I was able to successfully commit a transaction if I set the
serialization of the phoenix query server to JSON.
I will test more with protobufs and report back.
On 2/04/2016 1:11 AM, Steve Terrell wrote:
You might try looking up previous emails from me in this mailing
list. I had some
Hey Steve,
Thanks for your reply. I am using Phoenix 4.7.0 so these problem to be
fixed. Anyway, I did some more tests and noticed that the transactions
were timing out:
2016-04-02 09:58:28,189 INFO [tx-clean-timeout]
tephra.TransactionManager: Tx invalid list: added tx 145959104707900
You might try looking up previous emails from me in this mailing list. I
had some problems doing commits when using the thin client and Phoenix
4.6.0.
Hope this helps,
Steve
On Thu, Mar 31, 2016 at 11:25 PM, F21 wrote:
> As I mentioned about a week ago, I am working
As I mentioned about a week ago, I am working on a golang client using
protobuf serialization with the phoenix query server. I have
successfully dealt with the serialization of requests and responses.
However, I am trying to commit a transaction and just doesn't seem to
commit.
Here's what