Preparing to update gemfire links to geode [#130062377], some preliminary corrections to existing text
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/ebfed384 Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/ebfed384 Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/ebfed384 Branch: refs/staging/docs-grant1 Commit: ebfed384edcc99bb81f4688ee5b57a26bdd10d7d Parents: a432d8e Author: Dave Barnes <[email protected]> Authored: Tue Sep 20 12:16:10 2016 -0700 Committer: Dave Barnes <[email protected]> Committed: Tue Sep 20 12:16:10 2016 -0700 ---------------------------------------------------------------------- .../data_serialization/extending_the_autoserializer.html.md.erb | 2 +- developing/function_exec/chapter_overview.html.md.erb | 5 +++-- developing/function_exec/function_execution.html.md.erb | 2 +- 3 files changed, 5 insertions(+), 4 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/data_serialization/extending_the_autoserializer.html.md.erb ---------------------------------------------------------------------- diff --git a/developing/data_serialization/extending_the_autoserializer.html.md.erb b/developing/data_serialization/extending_the_autoserializer.html.md.erb index 3022221..8191787 100644 --- a/developing/data_serialization/extending_the_autoserializer.html.md.erb +++ b/developing/data_serialization/extending_the_autoserializer.html.md.erb @@ -27,7 +27,7 @@ You can customize the specific behaviors in `ReflectionBasedAutoSerializer` by o These methods are only called the first time the `ReflectionBasedAutoSerializer` sees a new class. The results will be remembered and used the next time the same class is seen. -For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/com/gemstone/gemfire/pdx/ReflectionBasedAutoSerializer.html)for details. +For details on these methods and their default behaviors, see the JavaDocs on [ReflectionBasedAutoSerializer](/releases/latest/javadoc/com/gemstone/gemfire/pdx/ReflectionBasedAutoSerializer.html) for details. ## <a id="concept_9E020566EE794A81A48A90BA798EC279__section_7C4CC39FD82A48A9B5F8376522078192" class="no-quick-link"></a>Example of Optimizing Autoserialization of BigInteger and BigDecimal Types http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/function_exec/chapter_overview.html.md.erb ---------------------------------------------------------------------- diff --git a/developing/function_exec/chapter_overview.html.md.erb b/developing/function_exec/chapter_overview.html.md.erb index e9cf671..ead23a9 100644 --- a/developing/function_exec/chapter_overview.html.md.erb +++ b/developing/function_exec/chapter_overview.html.md.erb @@ -5,14 +5,15 @@ title: Function Execution A function is a body of code that resides on a server and that an application can invoke from a client or from another server without the need to send the function code itself. The caller can direct a data-dependent function to operate on a particular dataset, or can direct a data-independent function to operate on a particular server, member, or member group. <a id="function_exec__section_CBD5B04ACC554029B5C710CE8E244FEA">The function execution service provides solutions for a variety of use cases, including:</a> + - An application needs to perform an operation on the data associated with a key. A registered server-side function can retrieve the data, operate on it, and put it back, with all processing performed locally to the server. - An application needs to initialize some of its components once on each server, which might be used later by executed functions. - A third-party service, such as a messaging service, requires initialization and startup. - Any arbitrary aggregation operation requires iteration over local data sets that can be done more efficiently through a single call to the cache server. - An external resource needs provisioning that can be done by executing a function on a server. -- **[How Function Execution Works](../../developing/function_exec/how_function_execution_works.html)** +- **[How Function Execution Works](how_function_execution_works.html)** -- **[Executing a Function in Apache Geode](../../developing/function_exec/function_execution.html)** +- **[Executing a Function in Apache Geode](function_execution.html)** http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ebfed384/developing/function_exec/function_execution.html.md.erb ---------------------------------------------------------------------- diff --git a/developing/function_exec/function_execution.html.md.erb b/developing/function_exec/function_execution.html.md.erb index 8cb9f0e..a881afd 100644 --- a/developing/function_exec/function_execution.html.md.erb +++ b/developing/function_exec/function_execution.html.md.erb @@ -40,7 +40,7 @@ Code the methods you need for the function. These steps do not have to be done i **Note:** When you use `PartitionRegionHelper.getLocalDataForContext`, `putIfAbsent` may not return expected results if you are working on local data set instead of the region. - 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/com/gemstone/gemfire/cache/execute/FunctionException.html/) for more information. + 4. To propagate an error condition or exception back to the caller of the function, throw a FunctionException from the `execute` method. Geode transmits the exception back to the caller as if it had been thrown on the calling side. See the Java API documentation for [FunctionException](/releases/latest/javadoc/com/gemstone/gemfire/cache/execute/FunctionException.html) for more information. Example function code:
