...

Motivation

Thin clients should be able to call invoke/invokeAll cache operations, which now available only for thick clients.

Description

Operations invoke [1] and invokeAll [2] are specified by JCache (JSR-107),  these operations Invoke an EntryProcessor against Cache.Entry's specified by the provided key/keys.

...

• EntryProcessor should be serialized to BinaryObject
• EntryProcessor's class  should be already deployed to the cluster (Deployment of entry processors code to the cluster is out of scope of this IEP)

Protocol changes

Operation codes

Two new client cache operations are required:

OP_CACHE_INVOKE message format

In case of such response we need some new error code to distinguish entry processor exceptions and and general client/server exceptions.

Alternatively, we can slightly extend response format (also for similarity with OP_CACHE_INVOKE_ALL response):

In this case introduction of the new error code is not required, entry processor exceptions will be indicated by success flag = false, and general client/server exceptions will be handled by response header flag and error code.   

OP_CACHE_INVOKE_ALL message format

Client-side API (java thin client)

The new methods should be added to ClientCache interface:

public interface ClientCache<K, V> {
	// ...

    public <T> T invoke(
        K key,
        EntryProcessor<K, V, T> entryProc,
        Object... arguments
    ) throws EntryProcessorException, ClientException;
    
    public <T> IgniteClientFuture<T> invokeAsync(
        K key,
        EntryProcessor<K, V, T> entryProc,
        Object... arguments
    ) throws ClientException;

    public <T> Map<K, EntryProcessorResult<T>> invokeAll(
        Set<? extends K> keys,
        EntryProcessor<K, V, T> entryProc,
        Object... args
    ) throws ClientException;

    public <T> IgniteClientFuture<Map<K, EntryProcessorResult<T>>> invokeAllAsync(
        Set<? extends K> keys,
        EntryProcessor<K, V, T> entryProc,
        Object... args
    ) throws ClientException;

	// ...
}

Risks and Assumptions

// Describe project risks, such as API or binary compatibility issues, major protocol changes, etc.

Discussion Links

https:// Links to discussions on the devlist, if applicable.lists.apache.org/thread/qrxmzcg5tvgot1tl2ko5x4qk08t51slf

Reference Links

[1]

[2]

Tickets