Hi j.david,
It seems that here is answer
http://apache-ignite-users.70518.x6.nabble.com/SQL-API-in-C-thin-client-td28128.html
Also, generally u...@ignite.apache.org mail list is suitable for such
questions. On dev list discussions related to contribution usually
take place.
вт, 28 мая 2019 г. в
Everything is in the title.
I'd like to either manipulate SQL queries or serialized Object on a distant
ignite cluster,
but so far, I only found how to define endPoints on the thin client
configuration (nothing equivalent
on the thick client).
I haven't found how to do anything else than
Denis Chudov created IGNITE-11874:
-
Summary: Fix mismatch between idle_verify results with and without
-dump option.
Key: IGNITE-11874
URL: https://issues.apache.org/jira/browse/IGNITE-11874
Project:
Ivan,
Yes, .NET client has such capability. Pavel Tupitsyn already mentions it in
this thread. As far as I understand, in .NET client implementation to
dispatch responses dedicated thread is used.
In a draft implementation of IGNITE-11685 I've used another approach: each
request thread can read a
Alex,
I am quite curious about async implementations from other clients. Is
there any design document describing such implementations? Does .NET
client have such capability?
Actually, I forgot to finish my previous message. One of my concerns
is that a concurrent response dispatch does not sound
Hi Ivan.
Thin client transactions support is not only for java thin client. There
are other clients, some of them already work in async mode.
Ticket IGNITE-11685 already has draft implementation too, but now it's
based on some changes to java thin client which were made by "transaction
support"
Hi Alex,
Regarding a problem with possible deadlock when two concurrent
transactions from the same client are trying to lock the same key and
an issue [1]. It seems to me that without fixing the issue [1] a
client transactions feature is not practical. Everyone who uses a
client from multiple
