[
https://issues.apache.org/jira/browse/IGNITE-13809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-13809:
------------------------------------
Description:
It's needed to add thin client support to Ignite Spring Cache integration.
To properly implement synchronous mode for Spring Cache manager, a lock that
guarantees synchronous value calculation for each cache key must be acquired on
the Ignite side in a distributed fashion.
As of now, we have no support for distributed locks for the thin client. So
it's proposed to leave Spring Cache synchronous mode unsupported if a thin
client is used to connecting to the Ignite cluster.
was:It would be perfect, if we add this feature, because now it is supported
only for client nodes, but not for thin clients.
> Add thin client support to Ignite Spring Cache integration
> ----------------------------------------------------------
>
> Key: IGNITE-13809
> URL: https://issues.apache.org/jira/browse/IGNITE-13809
> Project: Ignite
> Issue Type: New Feature
> Components: spring, thin client
> Affects Versions: 2.10
> Reporter: Ilya Shishkov
> Assignee: Mikhail Petrov
> Priority: Minor
>
> It's needed to add thin client support to Ignite Spring Cache integration.
> To properly implement synchronous mode for Spring Cache manager, a lock that
> guarantees synchronous value calculation for each cache key must be acquired
> on the Ignite side in a distributed fashion.
> As of now, we have no support for distributed locks for the thin client. So
> it's proposed to leave Spring Cache synchronous mode unsupported if a thin
> client is used to connecting to the Ignite cluster.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
