[MTCGA]: new failures in builds [6555113] needs to be handled
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 https://ci2.ignite.apache.org/test/1696779845262162419?currentProjectId=IgniteTests24Java8=%3Cdefault%3E No changes in the build - Here's a reminder of what contributors were agreed to do https://cwiki.apache.org/confluence/display/IGNITE/How+to+Contribute - Should you have any questions please contact dev@ignite.apache.org Best Regards, Apache Ignite TeamCity Bot https://github.com/apache/ignite-teamcity-bot Notification generated at 03:08:20 12-08-2022
[GitHub] [ignite-nodejs-thin-client] Mmuzaf merged pull request #7: IGNITE-15759 Replace local affinity function with the custom one
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: dev-unsubscr...@ignite.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
A new feedback has been added : 83
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
Re: [DISCUSSION] Thin client: Colocated Data Transactional Get
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.
On Thu, Aug 11, 2022 at 7:31 PM Alexei Scherbakov <
alexey.scherbak...@gmail.com> wrote:
> 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 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 functions [3].
> > - We do NOT have an option to execute a transactional operation on
> > affinity node [4], however, I think it is possilbe to send a
> > transactional get request over the affinity channels instead of the
> > default one.
> >
> >
> > The process execution on the thin client side may looks like:
> >
> > open transaction (colocated get request) -> set the right client
> > context -> pick up the affinity node channel (instead of the default
> > one) -> send the request over this channel right to the destination
> > primaries.
> >
> > The interface improvement may looks like:
> >
> > IgniteClient {
> > public void withAffinityNode(String cacheName, Object affKey);
> > }
> >
> > IgniteClient affClient = Ignition.startClient(new ClientConfiguration()
> > .setAddresses("node1_address:10800", "node2_address:10800",
> > "node3_address:10800"))
> > .withAffinityNode("person", "affKey");
> >
> > try (ClientTransaction tx = affClient.transactions().txStart()
> > ) {
> > ClientCache personCache = affClient.cache("person");
> > ClientCache paymentsCache =
> > affClient.cache("payments");
> >
> > // personCache.get("affKey");
> > // paymentsCache.get(..);
> > }
> > catch (ClientException e) {
> > // Ignore.
> > }
> >
> >
> > Additional benefits:
> >
> > - ScanQuery, SqlQuery with #setLocal(true) flag right on the required
> > affinity channel;
> > - ClientCompute task right on the required affinity channel;
> >
> >
> > WDYT?
> >
> >
> > [1]
> >
> https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation#affinity-colocation
> > [2]
> >
> https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#partition-awareness
> > [3] https://issues.apache.org/jira/browse/IGNITE-17316
> > [4]
> >
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/client/thin/TcpClientCache.java#L994
> >
>
>
> --
>
> Best regards,
> Alexei Scherbakov
>
Re: [DISCUSSION] Thin client: Colocated Data Transactional Get
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 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 functions [3].
> - We do NOT have an option to execute a transactional operation on
> affinity node [4], however, I think it is possilbe to send a
> transactional get request over the affinity channels instead of the
> default one.
>
>
> The process execution on the thin client side may looks like:
>
> open transaction (colocated get request) -> set the right client
> context -> pick up the affinity node channel (instead of the default
> one) -> send the request over this channel right to the destination
> primaries.
>
> The interface improvement may looks like:
>
> IgniteClient {
> public void withAffinityNode(String cacheName, Object affKey);
> }
>
> IgniteClient affClient = Ignition.startClient(new ClientConfiguration()
> .setAddresses("node1_address:10800", "node2_address:10800",
> "node3_address:10800"))
> .withAffinityNode("person", "affKey");
>
> try (ClientTransaction tx = affClient.transactions().txStart()
> ) {
> ClientCache personCache = affClient.cache("person");
> ClientCache paymentsCache =
> affClient.cache("payments");
>
> // personCache.get("affKey");
> // paymentsCache.get(..);
> }
> catch (ClientException e) {
> // Ignore.
> }
>
>
> Additional benefits:
>
> - ScanQuery, SqlQuery with #setLocal(true) flag right on the required
> affinity channel;
> - ClientCompute task right on the required affinity channel;
>
>
> WDYT?
>
>
> [1]
> https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation#affinity-colocation
> [2]
> https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#partition-awareness
> [3] https://issues.apache.org/jira/browse/IGNITE-17316
> [4]
> https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/client/thin/TcpClientCache.java#L994
>
--
Best regards,
Alexei Scherbakov
Ignite Summit Europe: The Call for Papers Is Open!
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 GMT). The event is hosted by GridGain Systems, with the Apache Software Foundation as a Community Partner. The summit is online and free. Share your Ignite experience with the Apache Ignite community that is based in the UK, Europe, and Asia! We are seeking technical content from in-memory computing practitioners: - An Ignite user story - An Ignite architectural deep dive - The experience of integrating Ignite with other technologies - The use of Ignite in a cloud environment - Ignite troubleshooting Submit your proposal for a 30-minute talk or for a 15-minutes lightning talk via https://sessionize.com/ignite-summit-europe/ Proposals are due by September 15, 2022. Kseniya Romanova, Apache Ignite PMC member [1] Summit website https://ignite-summit.org [2] Ignite Summit 2022 recordings https://youtube.com/playlist?list=PLMc7NR20hA-KqL1RCbsK1brtDGWzbvjyL
[DISCUSSION] Thin client: Colocated Data Transactional Get
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 functions [3].
- We do NOT have an option to execute a transactional operation on
affinity node [4], however, I think it is possilbe to send a
transactional get request over the affinity channels instead of the
default one.
The process execution on the thin client side may looks like:
open transaction (colocated get request) -> set the right client
context -> pick up the affinity node channel (instead of the default
one) -> send the request over this channel right to the destination
primaries.
The interface improvement may looks like:
IgniteClient {
public void withAffinityNode(String cacheName, Object affKey);
}
IgniteClient affClient = Ignition.startClient(new ClientConfiguration()
.setAddresses("node1_address:10800", "node2_address:10800",
"node3_address:10800"))
.withAffinityNode("person", "affKey");
try (ClientTransaction tx = affClient.transactions().txStart()
) {
ClientCache personCache = affClient.cache("person");
ClientCache paymentsCache = affClient.cache("payments");
// personCache.get("affKey");
// paymentsCache.get(..);
}
catch (ClientException e) {
// Ignore.
}
Additional benefits:
- ScanQuery, SqlQuery with #setLocal(true) flag right on the required
affinity channel;
- ClientCompute task right on the required affinity channel;
WDYT?
[1]
https://ignite.apache.org/docs/latest/data-modeling/affinity-collocation#affinity-colocation
[2]
https://ignite.apache.org/docs/latest/thin-clients/getting-started-with-thin-clients#partition-awareness
[3] https://issues.apache.org/jira/browse/IGNITE-17316
[4]
https://github.com/apache/ignite/blob/master/modules/core/src/main/java/org/apache/ignite/internal/client/thin/TcpClientCache.java#L994
