Hello igniters!

I've been working on a tutorial regarding Spring Cloud + Ignite and came across 
this issue:

IgniteRepositoryFactoryBean (Spring Data module) requires Ignite instance bean 
with specific name! And in the same time, Ignite autoconfiguration module 
provides Ignite instance bean with another name.
I propose a simple fix: remove constraints on a bean name and do injecting by 
class, as it is more Spring-way.
I created an issue (https://issues.apache.org/jira/browse/IGNITE-13169) and a 
pull request (https://github.com/apache/ignite/pull/7949).

These changes shouldn't break anything, as the injection still works, we just 
ask by class and not by name (bringing type safety in!).

Kind regards, 
Semyon.

Reply via email to