Hi Pavel, Thanks for the quick response.
I had looked at the ignite-3 github repo and could not find any reference to JSR 107, hence asked this question. Since Ignite 2.X is fully JSR 107 compliant, now the question is if ignite-3 is going to be the successor of Ignite 2.X and is going to 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:08 AM Pavel Tupitsyn <ptupit...@apache.org> wrote: > For now it does not have any of that. KeyValueView [1] is a table access > interface in Ignite 3 that is most similar to a "cache". > > > https://github.com/apache/ignite-3/blob/main/modules/api/src/main/java/org/apache/ignite/table/KeyValueView.java > > On Thu, May 30, 2024 at 6:19 PM Amit Jolly <amit.jo...@gmail.com> wrote: > >> HI, >> >> Will Apache Ignite 3.0 be compliant with JSR107 sepc? >> >> In particular, I am looking at the feature CacheEntryProcessor support in >> Ignite 3.0 >> >> >> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/IgniteCache.html#invoke-K-org.apache.ignite.cache.CacheEntryProcessor-java.lang.Object...- >> >> >> https://www.javadoc.io/doc/javax.cache/cache-api/latest/javax/cache/processor/EntryProcessor.html >> >> Thanks, >> >> Amit Jolly >> >
