You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Mikhail Petrov (Jira)" <ji...@apache.org> on 2020/11/09 15:39:00 UTC
[jira] [Commented] (IGNITE-13519) Add thin client support for
Spring Data.
[ https://issues.apache.org/jira/browse/IGNITE-13519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17228671#comment-17228671 ]
Mikhail Petrov commented on IGNITE-13519:
-----------------------------------------
[~alex_pl] Thanks a lot for the review.
> Add thin client support for Spring Data.
> ----------------------------------------
>
> Key: IGNITE-13519
> URL: https://issues.apache.org/jira/browse/IGNITE-13519
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Major
>
> It's needed to add thin client support for Spring Data.
> To work with a thin client it proposed:
> 1. Configure the bean of IgniteClient type
> 2. Pass the bean name from step 1 to the Spring Data repository configuration via the @RepositoryConfig annotation(igniteInstance = "<bean name for accessing the Ignite cluster").
> At the moment, the repository configuration which uses node to access the cluster is performed in the same way.
> When using a node to access a cluster, you can configure TextQuery execution. This functionality does not support the thin client - if repository is configures to use TextQuery and thin client is used to access the cluster, repository method for TextQuery will fail with an error in runtime.
> All other operations implemented for the node are supported in the case of using the thin client.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)