[ 
https://issues.apache.org/jira/browse/IGNITE-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16028604#comment-16028604
 ] 

ASF GitHub Bot commented on IGNITE-5030:
----------------------------------------

GitHub user mcherkasov opened a pull request:

    https://github.com/apache/ignite/pull/2030

    IGNITE-5030 Support Spring @Cacheable(sync=true) annotation

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite IGNITE-5030

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/2030.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 #2030
    
----
commit 37ae9bf51aa68a17a41199df6c41897fda1c7cd3
Author: mcherkasov <[email protected]>
Date:   2017-05-29T17:29:28Z

    Added support for sync option in @Cacheable annotation

----


> 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: Mikhail Cherkasov
>
> @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)

Reply via email to