Re: How to use ClusterNodeAttributeAffinityBackupFilter to have atleast one replica in second zone

rs = new HashSet<>(); > > for (ClusterNode node : previouslySelected) { > if (Objects.equals(candidate.attribute(attrName), > node.attribute(attrName)) && > !usedAttrs.add(candidate.attribute(attrName))) > return false; > } > >

Re: How to use ClusterNodeAttributeAffinityBackupFilter to have atleast one replica in second zone

ttributes = new HashMap<>(); userAttributes.put("AVAILABILITY_ZONE", "ZONE2"); IgniteConfiguration cfg = new IgniteConfiguration(); cfg.setUserAttributes(userAttributes); Ignition.start(cfg); https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/cache/affinity/rendez

How to use ClusterNodeAttributeAffinityBackupFilter to have atleast one replica in second zone

er Thanks, Amit Jolly

Re: Ignite H2 to Calcite issues

Hi Alex, Also looks like the query does work with this error/warning. But not sure what's the implication on the result or overall performance. Thanks, Amit Jolly On Fri, Aug 16, 2024 at 10:03 AM Amit Jolly wrote: > Hi Alex, > > Find below the details you requested. > >

Re: Ignite H2 to Calcite issues

d = 1098 IgniteIndexScan(table=[[PUBLIC, ORDERSTOMATCH]], index=[_key_PK], requiredColumns=[{0}], inlineScan=[false], collation=[[0 ASC-nulls-first]]): rowcount = 1.0, cumulative cost = IgniteCost [rowCount=1.0, cpu=1.0, memory=1.0, io=1.0, network=1.0], id = 1087 It is using Index scan. Thanks, A

Re: Ignite H2 to Calcite issues

new ArrayList<>(); @QuerySqlField private List sellOrders = new ArrayList<>(); } Order.java import lombok.Data; import java.io.Serializable; @Data public class Order implements Serializable { private String direction; // BUY or SELL private Integer qty; } T

Ignite H2 to Calcite issues

e-2.16.0.jar:2.16.0] at org.apache.ignite.internal.processors.query.calcite.exec.QueryTaskExecutorImpl.lambda$execute$0(QueryTaskExecutorImpl.java:66) ~[ignite-calcite-2.16.0.jar:2.16.0] Any idea what might be causing this? Regards, Amit Jolly

Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?

*Continues query cache*, while going through the code of 3.0, I could not find/validate whether these features will be supported in 3.0 or not. Is there any matrix which explains/shows feature to feature comparison between 2.X and 3.0? Thanks, Amit Jolly On Mon, Jun 3, 2024 at 1:41 AM Pavel Tupitsyn

Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?

replace Ignite 2.X in future, will Ignite 3 be JSR 107 compliant as well? If yes, do we have timelines when ignite-3 will be JSR 107 compliant, If no, what will be the migration strategy for the current Ignite 2.X user using features listed in JSR 107. Thanks, Amit Jolly On Fri, May 31, 2024 at 12

Will Apache Ignite 3.0 be compliant with JSR107 sepc?

-java.lang.Object...- https://www.javadoc.io/doc/javax.cache/cache-api/latest/javax/cache/processor/EntryProcessor.html Thanks, Amit Jolly