[
https://issues.apache.org/jira/browse/IGNITE-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14278838#comment-14278838
]
Sergey Evdokimov commented on IGNITE-59:
----------------------------------------
Text from mail conversation:
Sergey E: Will we support lockAsync() on IgniteCache? Should I remove all tests
that check lockAsync() methods?
Dmitriy: We should support it through our standard async support. I will take a
closer look at the design and will provide more detail.
Sergey E: Will be exists GridCacheEntry.isLocked() ,
GridCacheEntry.isLockedByThread() ? If true we need the method to get entry by
key on IgniteCache (analog of GridCacheProjection.entry(K key)).
Dmitriy: These methods will not exist on GridCacheEntry.
Sergey E: In current IgniteCache interface lock() returns
java.util.concurrent.locks.Lock . May be 'lock()' should return something like
CacheLock, that extends java.util.concurrent.locks.Lock and contains additional
methods like "isLocked()", "isLockedByThread()". Thoughts? Now IgniteCache
contains "isLocked(key)", "isLockedByThread(keys)" methods.
Sergey E: Why lockAll(Set) take a Set, may be it should take Collection ?
> Support lock, lockAll
> ---------------------
>
> Key: IGNITE-59
> URL: https://issues.apache.org/jira/browse/IGNITE-59
> Project: Ignite
> Issue Type: Sub-task
> Components: cache
> Reporter: Semen Boikov
> Assignee: Sergey Evdokimov
> Fix For: sprint-1
>
>
> Implement methods on IgniteCache: 'Lock lock(K key)', 'Lock lockAll(Set<?
> extends K> keys)', note: in new design method return Lock instance.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
