Hi, So the issue here is in order to use Ignite as key-value Cache API along with Spring Repository we have to let the spring application context initialize fully and then need to start ignite instance passing the application context.
In order to use Ignite as Spring Cache provider the SpringCacheManager starts its own ignite instance which would be different than the one started earlier for key-value caching api. Is there any way where we can pass the already running ignite instance (one for caching api) to the Spring Cache Manager and it does not try to create that instance again? I see the onApplicationEvent method in SpringCacheManager where its starting Ignite node with Spring Application Context.(*IgniteSpring.start(cfgPath, springCtx)*) Please check onApplicationEvent(ContextRefereshedEvent event) in SpringCacheManager. In this method from where it gets ApplicationContext instance? Is there any way we can externally pass the application context.? The last option would be to start a new ignite instance from SpringCacheManager. This might be silly question but would there be a different node running (along with one running for cache api) or a different grid within the same node? Thank you in advance. Regards Monil -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
