when you mean these annotations do you mean this would need to be implemented in ignite?
The project at the moment is split into multiple modules. ignite-core, ignite-cache, etc ... The plan was to also have ignite-data but that will take a bit of work to get working correctly but the basic config is mostly done. The plan is also to verify the API described in the wiki and make sure this is what would work best. At the moment I'm missing an implementation for the thin-cache and how that would fit into this scheme. I've removed it due to the added complexity but I'm sure something could be arranged that would work. For Ignite-cache, I have it as a separate module that can be optionally included in a micronaut project where this module also has a dependency on micronaut-cache. The AsyncCache and SyncCache are the two interfaces that micronaut-cache defines. There are two ways to define the implementation, you can either provide beans for AsyncCache and SyncCache but they also define a DynamicCacheManager that will use the name of the instance to refer to the name of the cache used. In the documentation I believe for Teracotta you give a list of caches you want and Hazelcast implements the DynamicCacheManager. you can see that in the yaml configuration in micronaut documentation where a list of cache names are provided along with a configuration. Something similar can also be setup where a list of implementations from the yaml can be mapped to a configuration if that would be more ideal. https://github.com/pollend/micronaut-ignite/tree/feature/rework/ignite-cache/src/main/java/io/micronaut/ignite On Sat, Aug 15, 2020 at 4:10 PM Saikat Maitra <saikat.mai...@gmail.com> wrote: > Hi Michael, > > Welcome to the Ignite community!!! > > Please feel free to reach out if you have any questions with respect to > Ignite Integration. > > I had a question specific to integration and wanted to ask if these > annotations also need to be implemented for the micronaut-ignite > integration. > > @Cacheable - Indicates a method is cacheable within the given cache name > @CachePut - Indicates that the return value of a method invocation should > be cached. Unlike @Cacheable the original operation is never skipped. > @CacheInvalidate - Indicates the invocation of a method should cause the > invalidation of one or many caches. > > Denis - Thank you for sharing the details in dev list, it great to learn > about micronaut-ignite module. > > Regards, > Saikat > > On Sat, Aug 15, 2020 at 12:35 AM Michael Pollind <mpoll...@gmail.com> > wrote: > > > Here is the page that i've stubbed out: > > https://cwiki.apache.org/confluence/display/IGNITE/Micronaut+Integration > > > > I'll start trying to fill out some of the details over the next few days > > and we can go from there. > > > > On Fri, Aug 14, 2020 at 2:47 PM Denis Magda <dma...@apache.org> wrote: > > > > > You're in, now you can create wiki pages in the Ignite namespace. > > > > > > Also, please subscribe to the list by sending a note to the > > > dev-subscr...@ignite.apache.org address. Otherwise, we need to approve > > > every email you send. > > > > > > - > > > Denis > > > > > > > > > On Fri, Aug 14, 2020 at 2:43 PM Michael Pollind <mpoll...@gmail.com> > > > wrote: > > > > > >> > > >> > > >> here is the link: > > >> > > >> > > > https://cwiki.apache.org/confluence/users/viewuserprofile.action?username=mpollind > > >> > > >> Here is the work in progress pull request that I've put together: > > >> https://github.com/micronaut-projects/micronaut-ignite/pull/33 > > >> > > >> > > >> > > >> -- > > >> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/ > > >> > > > > > >
