You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/02/23 19:02:13 UTC

[jira] [Created] (IGNITE-326) Need to add IgniteEntryProcessor and a new invoke method

Dmitriy Setrakyan created IGNITE-326:
----------------------------------------

             Summary: Need to add IgniteEntryProcessor and a new invoke method
                 Key: IGNITE-326
                 URL: https://issues.apache.org/jira/browse/IGNITE-326
             Project: Ignite
          Issue Type: Improvement
          Components: cache
            Reporter: Dmitriy Setrakyan
            Assignee: Yakov Zhdanov
            Priority: Blocker
             Fix For: sprint-2


>From dev list thread:
{noformat}
I just checked this - a new method with IgniteEntryProcessor is called.

On Sun, Feb 22, 2015 at 11:28 PM, Dmitriy Setrakyan <ds...@apache.org>
wrote:

> Hello Ignite experts,
>
> I just noticed that EntryProcessor does not implement Serializable, which
> makes it impossible to serialize when used in Java8 lambda notations.
>
> However, what if we define IgniteEntryProcessor which extends both,
> EntryProcessor and Serializable? And also add invoke method on IgniteCache
> which accepts IgniteEntryProcessor, like so:
> ----------------
> *@IgniteAsyncSupported*
> *public <T> T invoke(K key, IgniteEntryProcessor<K, V, T> entryProcessor,
> Object... arguments);*
>
>
> *@IgniteAsyncSupported*
> *@Override public <T> T invoke(K key, EntryProcessor<K, V, T>
> entryProcessor, Object... arguments);*
> ------------------
>
> Does anyone know which method will be invoked when used with Java8 lambdas
> without any casting, like so (is it JDK specific?):
> -------------------
> *cache.invoke("mykey", (entry, args) -> { .... }); *
> -------------------
>
> D.
{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)