ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dmitriy Setrakyan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3222) IgniteCache.invokeAll for all cache entries
Date Wed, 01 Jun 2016 00:19:12 GMT

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

Dmitriy Setrakyan commented on IGNITE-3222:

I actually believe that such method will be error-prone and will cause all sorts of memory
issues for users trying to execute this method over large caches.

What we need instead is an affinityCall/Run method over a partition, not a key. Why not provide
this method instead?

> IgniteCache.invokeAll for all cache entries
> -------------------------------------------
>                 Key: IGNITE-3222
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3222
>             Project: Ignite
>          Issue Type: Task
>          Components: cache
>    Affects Versions: 1.1.4
>            Reporter: Pavel Tupitsyn
>             Fix For: 1.7
> Implement an invokeAll overload that processes all cache keys (not some specific set).
> Proposed signature:
> {code}
> public void invokeAll(CacheEntryProcessor<K, V, T> entryProcessor, Object... args);
> public <T> Map<K, EntryProcessorResult<T>> invokeAll(CacheEntryProcessor<K,
V, T> entryProcessor, boolean returnAffectedOnly, Object... args);
> {code}
> This will apply the specified processor to all cache entries.
> First method does not return anything.
> Second method either returns all results for all entries, or only for entries that have
been changed by the processor in any way.

This message was sent by Atlassian JIRA

View raw message