GemFire 6.0.1

Package com.gemstone.gemfire.cache.execute

The com.gemstone.gemfire.cache.execute package provides APIs used for function execution on gemfire system members.

See:
          Description

Interface Summary
Execution Provides methods to build the context for the execution of a Function.
Function Defines the interface a user defined function implements.
FunctionContext Defines the execution context of a Function.
RegionFunctionContext Defines the execution context of a data dependent Function.
ResultCollector<T extends Serializable> Defines the interface for a container that gathers results from function execution.
ResultSender<T extends Serializable> Provides methods to send results back to the ResultCollector.
 

Class Summary
FunctionAdapter Application developers can extend this class instead of implementing the Function interface.
FunctionService Provides the entry point into execution of user defined Functions.
 

Exception Summary
FunctionException Thrown to indicate incorrect execution of Functions in GemFire.
FunctionInvocationTargetException Thrown if one of the function execution nodes goes away or cache is closed Function needs to be re-executed again if the Throwable.getCause() is FunctionInvocationTargetException.
 

Package com.gemstone.gemfire.cache.execute Description

The com.gemstone.gemfire.cache.execute package provides APIs used for function execution on gemfire system members.

GemFire's Function Execution Service supports execution of user-defined methods on targeted GemFire system members.
The fundamental premise is to route the function transparently to the GemFire system member that hosts the data subset required by the application function and avoid moving data around on the network. Application function can be executed on just one fabric node, executed in parallel on a subset of nodes or in parallel across all the nodes.

The Function Execution Service API is based on the following classes and interfaces which work together to provide the function execution capability. The API allows execution of functions that are "data dependent" or "data independent". Data dependent functions are functions that need access to the local data set, on the targeted member.

Example of a "data dependent" execution using the Function Execution Service

    Region region;
    Set keySet = Collections.singleton("myKey");
    Function multiGetFunction;
    Serializable args;
    ResultCollector rc = FunctionService.onRegion(region)
                                        .withArgs(args)
                                        .withFilter(keySet)
                                        .withCollector(new MyCustomResultCollector())
                                        .execute(multiGetFunction.getId());
    // Application can do something else here before retrieving the result
    // It can even get deal with partial results which it will get in
    // MyCustomResultCollector.addResult().
    
    Serializable functionResult = rc.getResult();

Example of a "data independent" execution using the Function Execution Service

    DistributedSystem ds;
    Function memberSetupFunction;
    Serializable args;
    ResultCollector rc = FunctionService.onMembers(ds)
                                        .withArgs(args)
                                        .execute(memberSetupFunction.getId());
    //Application can do something else here before retrieving the result
    Serializable functionResult = rc.getResult();

Example of a "Function" to be executed which sends result to ResultCollector using ResultSender.


        public class MYFunction extends FunctionAdapter {
        
          public void execute(FunctionContext context) {
                for(int i =0 ;i< 10; i++)        
                        context.getResultSender().sendResult(i);
                context.getResultSender.lastResult(10);
          }
        
          public String getId() {
            return "MYFunction";
          }
        
          public boolean hasResult() {
            return true;
          }
        
        }

Some scenarios where function execution can be useful:

  1. Any arbitrary aggregation operation that requires iteration over local data sets done more efficiently through a single call to the cache server
  2. Application wants to execute a server side behaviour.
  3. Application wants to initialize some of its components once on each server which might be used later by executed functions, for example initialization of a 3rd party service.


GemFire 6.0.1

Copyright © 2002-2009 GemStone Systems, Inc. All Rights Reserved.