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 2374359 GEODE-4728: Docs - Region attributes edit 2374359 is described below commit 23743599c8f05c52442ab58ec98fdeb024bf1be3 Author: Dave Barnes <dbar...@pivotal.io> AuthorDate: Fri Apr 27 08:46:26 2018 -0700 GEODE-4728: Docs - Region attributes edit --- .../client-cache/application-plugins.html.md.erb | 9 ++++----- .../regions/region-attributes.html.md.erb | 23 ++++++++-------------- 2 files changed, 12 insertions(+), 20 deletions(-) diff --git a/docs/geode-native-docs/client-cache/application-plugins.html.md.erb b/docs/geode-native-docs/client-cache/application-plugins.html.md.erb index cbb2196..9e453bd 100644 --- a/docs/geode-native-docs/client-cache/application-plugins.html.md.erb +++ b/docs/geode-native-docs/client-cache/application-plugins.html.md.erb @@ -87,17 +87,16 @@ class DisconnectCacheListener : public CacheListener ## <a id="application-plugins_partitionresolver" class="no-quick-link"></a>PartitionResolver -This section pertains to data access in server regions that have custom partitioning. Custom partitioning uses a Java `PartitionResolver` to colocate like data in the same buckets. For the client, you can use a `PartitionResolver` that matches the server's implementation to access data in a single hop. With single-hop data access, the client pool maintains information on where a partitioned region's data is hosted. When accessing a single entry, the client directly contacts the server th [...] +This section pertains to data access in server regions that have custom partitioning. Custom partitioning uses a Java `PartitionResolver` to colocate like data in the same buckets. For the client, you can use a `PartitionResolver` that matches the server's implementation to access data in a single hop. With single-hop data access, the client pool maintains information on where a partitioned region's data is hosted. When accessing a single entry, the client directly contacts the server th [...] **Note:** Single hop is used for the following operations: `put`, `get`, `destroy`, `putAll`, `getAll`, `removeAll` and `onRegion` function execution. **Implementing Single-Hop on a Partitioned Region** -1. Make sure the pool attribute, `pr-single-hop-enabled`, is set to `true` or not set. It is `true` by default. -2. If the server uses a custom `PartitionResolver` install an implementation of `PartitionResolver` in the client region that returns, entry for entry, the same value as the server's Java `PartitionResolver` implementation. The server uses the resolver to colocate like data within a partitioned region. - - If the server does not use a custom resolver, the default resolvers in client and server match, so single hop will work there by default. +- Make sure the pool attribute, `pr-single-hop-enabled`, is set to `true` or not set. It is `true` by default. +- If the server uses a custom `PartitionResolver` install an implementation of `PartitionResolver` in the client region that returns, entry for entry, the same value as the server's Java `PartitionResolver` implementation. The server uses the resolver to colocate like data within a partitioned region. +- If the server does not use a custom resolver, the default resolvers in client and server match, so single hop will work there by default. Disable single hop behavior for a region by setting its pool attribute `pr-single-hop-enabled` to `false`. diff --git a/docs/geode-native-docs/regions/region-attributes.html.md.erb b/docs/geode-native-docs/regions/region-attributes.html.md.erb index dbaf2ae..7045abd 100644 --- a/docs/geode-native-docs/regions/region-attributes.html.md.erb +++ b/docs/geode-native-docs/regions/region-attributes.html.md.erb @@ -126,6 +126,7 @@ You can configure the most common of these options with the predefined region at [Region Shortcuts](#region-shortcuts) and the API docs for `RegionShortcut`. If `CachingEnabled` is false (no caching), an `IllegalStateException` is thrown if any of these cache behavior attributes are set: + - [InitialCapacity](#initial-capacity) - [EntryTimeToLive](../client-cache/expiration-attributes.html#expiration-attributes) - [EntryIdleTimeout](../client-cache/expiration-attributes.html#expiration-attributes) @@ -184,32 +185,24 @@ The following declaration sets the region's `ConcurrencyLevel` to `16`: **Note:** When `CachingEnabled` is `false`, do not set the `ConcurrencyLevel` attribute. An `IllegalStateException` is thrown if the attribute is set. -- **[DiskPolicy](../client-cache/disk-policy.html)** - -- **[PersistenceManager](../client-cache/persistence-manager.html)** - - ## <a id="mutable-region-attributes"></a>Mutable Region Attributes Mutable region attributes identify expiration and cache listener, cache writer and cache loader -actions that are run from the defining client. The next table lists the mutable attributes that +actions that are run from the defining client. The following table lists the mutable attributes that generally can be modified after region creation by using the `AttributesMutator` for the region. -| Mutable Region Attribute | Default Setting | -|---------------------------------------------------------------------|-----------------| -| Expiration attributes. See [Specifying Expiration Attributes](expiration-attributes.html#expiration-attributes). | no expiration | -| [LruEntriesLimit](#lru-entries-limit) | 0 (no limit) | +| Mutable Region Attribute | Default Setting | +|----------------------------------------------------------------------------------------------|-----------------| +| [Expiration attributes](expiration-attributes.html#expiration-attributes). | no expiration | +| [LruEntriesLimit](#lru-entries-limit) | 0 (no limit) | | [CacheLoader](../client-cache/application-plugins.html#application-plugins_cacheloader) | | | [CacheWriter](../client-cache/application-plugins.html#application-plugins_cachewriter) | | -| [CacheListener](../client-cache/application-plugins.html#application-plugins_cachelistener) | | +| [CacheListener](../client-cache/application-plugins.html#application-plugins_cachelistener) | | -See [AttributesMutator](application-plugins.html#application-plugins_attributesmutator) for +See [AttributesMutator](../client-cache/application-plugins.html#application-plugins_attributesmutator) for information about using `AttributesMutator` with cache listeners, cache loaders, and cache writers. -The remainder of this section examines these attributes in detail. Throughout the descriptions, -`cache.xml` file snippets show how each attribute can be set declaratively. - ### <a id="concurrency-checks-enabled"></a>ConcurrencyChecksEnabled This attribute determines whether members perform checks to provide consistent handling for -- To stop receiving notification emails like this one, please contact dbar...@apache.org.