[
https://issues.apache.org/jira/browse/IGNITE-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15978466#comment-15978466
]
ASF GitHub Bot commented on IGNITE-5030:
----------------------------------------
GitHub user daradurvs opened a pull request:
https://github.com/apache/ignite/pull/1852
IGNITE-5030
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/daradurvs/ignite ignite-5030
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/1852.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1852
----
commit 958749be996e531a05fa5afd284aadd9e9838359
Author: Vyacheslav Daradur <[email protected]>
Date: 2017-04-21T10:28:56Z
ignite-5030: the method was implemented
----
> Support Spring @Cacheable(sync=true) annotation
> -----------------------------------------------
>
> Key: IGNITE-5030
> URL: https://issues.apache.org/jira/browse/IGNITE-5030
> Project: Ignite
> Issue Type: Task
> Reporter: Anton Vinogradov
> Assignee: Vyacheslav Daradur
>
> @Cacheable(sync=true) guarantee that only one thread (across the cluster)
> will fetch value for a key on get, even in case of some simultaneous gets.
> So,
> org.apache.ignite.cache.spring.SpringCache#get(java.lang.Object,
> java.util.concurrent.Callable<T>)
> should be implemented to provide such guarantee.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
