Hi Igniters,
I've detected some new issue on TeamCity to be handled. You are more than
welcomed to help.
*New test failure in master
IgniteCacheQueryStopOnCancelOrTimeoutDistributedJoinSelfTest.testCancel2
Mmuzaf merged PR #7:
URL: https://github.com/apache/ignite-nodejs-thin-client/pull/7
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
A new feedback has been added, go to bugyard.io to see all the details...
https://bugyard.io
A new feedback has been added
"GitHub 404 error on documentation link" by vgoudkov
View feedback
https://app.bugyard.io/web/app/rycqZJDyY/f/62f54c2975624400143080c1
Compute API requires code deployment, which may be an obstacle in some
cases.
But instead of withAffinityNode, I think we can add a new method to
IgniteClient:
public ClientTransactions transactions(ClusterGroup grp);
Similar to existing compute(ClusterGroup) and services(ClusterGroup)
methods.
Moving transaction logic to the client seems to me a bad idea.
I would instead send the transaction's code close to data using Compute API.
чт, 11 авг. 2022 г. в 17:54, Maxim Muzafarov :
> Igniters,
>
>
> I'd like to discuss with you some thoughts about getting colocated
> data [1] from nodes
Hi, Igniters!
Ignite Summit 2022 went great—recordings are available at your
convenience[2]. And, now, we're ready to turn our attention to Ignite
Summit 2022 Europe!
Ignite Summit 2022 Europe will be delivered over two days, November 9 and
10 (each day from approximately 9:30 AM GMT to 1:00 PM
Igniters,
I'd like to discuss with you some thoughts about getting colocated
data [1] from nodes via thin client (mostly the java thin client).
- We do have partition awareness enabled for non-transactional data [2].
- We do have from now on partition awareness for caches with custom
affinity
