You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Pavlukhin (Jira)" <ji...@apache.org> on 2020/02/04 12:02:00 UTC
[jira] [Commented] (IGNITE-12582) It is needed to set used cache
for Spring Data dynamically
[ https://issues.apache.org/jira/browse/IGNITE-12582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17029794#comment-17029794 ]
Ivan Pavlukhin commented on IGNITE-12582:
-----------------------------------------
[~schernolyas], thank you for your efforts! I looked into [PR|https://github.com/apache/ignite/pull/7347/] and I have some questions:
# Can we use {{org.springframework.beans.factory.support.AbstractBeanFactory#getBeanExpressionResolver}} for an expression evaluation? Generally it sounds good to have a behavior consistent with {{@Value}} annotation.
# I suppose the next question was discussed somehow but it would good to reflect it in the ticket. Why do we reuse old {{@RepositoryConfig}} annotation enhancing it with new capabilities? Theoretically it can lead to backward incompatibility. Other options here are adding a new annotation and deprecating the old one or adding a new property to the existing annotation.
> It is needed to set used cache for Spring Data dynamically
> ----------------------------------------------------------
>
> Key: IGNITE-12582
> URL: https://issues.apache.org/jira/browse/IGNITE-12582
> Project: Ignite
> Issue Type: Improvement
> Components: spring
> Affects Versions: 2.7.6
> Reporter: Sergey Chernolyas
> Assignee: Sergey Chernolyas
> Priority: Major
>
> Hi!
> My project needs to configure used cache by property, like ""[spring.data|http://spring.data/].mongodb.uri: mongodb://<user>:<passwd>@<host>:<port>/<dbname>" from Spring Data for MongoDB. Now, I can set cache for particular repository by annotation "RepositoryConfig" only.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)