[
https://issues.apache.org/jira/browse/IGNITE-13169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17141889#comment-17141889
]
Manuel Núñez edited comment on IGNITE-13169 at 6/22/20, 10:26 AM:
------------------------------------------------------------------
Please, take a look at IGNITE-13005. Supports different mechanism (Ignite
instance name, Ignite configuration name and Ignite configuration file) to
discover Ignite Instances. Also supports working with multiple Ignite Instances
on same JVM.
was (Author: mnusan):
Please, take a look at IGNITE-13005.
> Remove Ignite bean name requirement for Spring Data Repository
> --------------------------------------------------------------
>
> Key: IGNITE-13169
> URL: https://issues.apache.org/jira/browse/IGNITE-13169
> Project: Ignite
> Issue Type: Improvement
> Components: springdata
> Affects Versions: 2.8.1
> Reporter: Semyon Danilov
> Assignee: Semyon Danilov
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> At the moment IgniteRepositoryFactoryBean requires Ignite instance bean (or
> IgniteConfiguration instance bean) with specific name.
> There are couple of problems with that behavior:
> 1) We have a SpringBoot autoconfiguration module which creates bean with
> different name, so Ignite Spring Data won't work out of the box
> 2) That is, actually, not a Spring-way to do things: Spring prefers
> injecting by class, qualifiers like name and order should be used only when
> necessay
> I propose changing behavior to "getting bean by class and not by name"
>
> This won't require any user code changes, because we only remove restrictions
> on Ignite instance bean name
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
