@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
Hey Constantin,
Yeah, I realized that there won't be a quick solution to the issue. There
have been patterns that I got to know when trying out various things. As
you said I will have to tune the queries and/or the cluster and keep trying.
Regards,
Amit
P.S - will connect with you separately.