Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?
The way that clients operate is quite different in AI3. You can't assume the same thick/thin distinction. There are two answers to your question: 1. Ignite 2 will continue to be available. Version 3 is a big update and it's unlikely that everyone will move over on day 1. So if you like AI2, it's safe to use it 2. Ignite 3 is currently in beta, so no one can give you definitive answers. However, the goal is that AI3 will support the same (and more!) workloads as 2, although the way you achieve the functionality may differ On Mon, 3 Jun 2024 at 22:43, Amit Jolly wrote: > Hi Pavel, > > Thanks for the quick response. > > We are currently evaluating Apache Ignite for our project and are planning > to use features like *CacheEntryProcessor*, *Thick clients with Near > Cache *(Looks like 3.0 will only have thin clients and near cache is only > supported in thick clients) and *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 > wrote: > >> Amit, unfortunately, I don't have answers at the moment. >> >> I think a JSR107 wrapper can be developed on top of existing Ignite 3 >> APIs (Table + Compute), including CacheEntryProcessor support, but we don't >> have specific plans for now. >> >> On Fri, May 31, 2024 at 4:34 PM Amit Jolly wrote: >> >>> 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 >>> 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 >>>> 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 >>>>> >>>>
Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?
Hi Pavel, Thanks for the quick response. We are currently evaluating Apache Ignite for our project and are planning to use features like *CacheEntryProcessor*, *Thick clients with Near Cache *(Looks like 3.0 will only have thin clients and near cache is only supported in thick clients) and *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 wrote: > Amit, unfortunately, I don't have answers at the moment. > > I think a JSR107 wrapper can be developed on top of existing Ignite 3 APIs > (Table + Compute), including CacheEntryProcessor support, but we don't have > specific plans for now. > > On Fri, May 31, 2024 at 4:34 PM Amit Jolly wrote: > >> 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 >> 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 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 >>>> >>>
Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?
Amit, unfortunately, I don't have answers at the moment. I think a JSR107 wrapper can be developed on top of existing Ignite 3 APIs (Table + Compute), including CacheEntryProcessor support, but we don't have specific plans for now. On Fri, May 31, 2024 at 4:34 PM Amit Jolly wrote: > 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 > 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 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 >>> >>
Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?
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 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 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 >> >
Re: Will Apache Ignite 3.0 be compliant with JSR107 sepc?
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 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 >
Will Apache Ignite 3.0 be compliant with JSR107 sepc?
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
