You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2019/02/14 01:34:59 UTC

[geode-native] branch develop updated: GEODE-4728 - User Guide, Incorporate reviewer suggestions

This is an automated email from the ASF dual-hosted git repository.

dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode-native.git


The following commit(s) were added to refs/heads/develop by this push:
     new 9c463ba  GEODE-4728 - User Guide, Incorporate reviewer suggestions
9c463ba is described below

commit 9c463ba2b35bdc44d8a2feed09aaca54ed8df136
Author: Dave Barnes <db...@pivotal.io>
AuthorDate: Wed Feb 13 17:27:51 2019 -0800

    GEODE-4728 - User Guide, Incorporate reviewer suggestions
---
 docs/geode-native-docs/function-execution.html.md.erb | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/docs/geode-native-docs/function-execution.html.md.erb b/docs/geode-native-docs/function-execution.html.md.erb
index e30dddc..da7301b 100644
--- a/docs/geode-native-docs/function-execution.html.md.erb
+++ b/docs/geode-native-docs/function-execution.html.md.erb
@@ -33,7 +33,7 @@ The client must connect to the server through a connection pool in order to invo
 
 ## <a id="how_functions_execute"></a>How Functions Execute
 
-1.  The calling client application runs the `execute` method on the `Execution` object. The object must already be registered on the servers.
+1.  The calling client application runs the `execute` method on the `Execution` object. The function must already be registered on the servers.
 2.  The function is invoked on all servers where it needs to run. The locations are determined by the `FunctionService on*` 
 method calls, region configuration, and any filters.
 3.  If the function has results, the result is returned in a `ResultCollector` object.
@@ -45,14 +45,13 @@ In every client where you want to execute the function and process the results:
 `onRegion`, `onServer` and `onServers`, define the highest level where the function is run. If
 you use `onRegion` you can further narrow your run scope by setting key filters. The function run
 using `onRegion` is a data dependent function – the others are data-independent functions.
-
-You can run a data dependent function against custom partitioned and colocated partitioned regions. From the client, provide the appropriate key
+You can run a data dependent function against partitioned and colocated partitioned regions. From the client, provide the appropriate key
  sets to the function call.
 
 -  Use the `Execution` object as needed for additional function configuration. You can:
     -   Provide a set of data keys to `withFilter` to narrow the execution scope. This works only for `onRegion` Execution objects.
     -   Provide function arguments to `withArgs`.
-    -   Define a custom `ResultCollector` to `withCollector`.
+    -   Provide a custom `ResultCollector` to `withCollector`.
 
 -  Call the `Execution` object execute method to run the function.
 
@@ -108,7 +107,7 @@ The client:
 - invokes the object's execute method to invoke the server-side function.
 
 If the client expects results, it must create a result
-object. Optionally, the client can use a provided result collector which offers some predefined
+object. Optionally, the client can use a provided ResultCollector which offers some predefined
 methods for iterating over and processing return values.
 
 ## <a id="dotnet_example"></a>.NET Example