gora-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From build...@apache.org
Subject svn commit: r995863 - in /websites/staging/gora/trunk/content: ./ current/gora-jcache.html
Date Thu, 25 Aug 2016 07:10:00 GMT
Author: buildbot
Date: Thu Aug 25 07:10:00 2016
New Revision: 995863

Log:
Staging update by buildbot for gora

Modified:
    websites/staging/gora/trunk/content/   (props changed)
    websites/staging/gora/trunk/content/current/gora-jcache.html

Propchange: websites/staging/gora/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Thu Aug 25 07:10:00 2016
@@ -1 +1 @@
-1757613
+1757615

Modified: websites/staging/gora/trunk/content/current/gora-jcache.html
==============================================================================
--- websites/staging/gora/trunk/content/current/gora-jcache.html (original)
+++ websites/staging/gora/trunk/content/current/gora-jcache.html Thu Aug 25 07:10:00 2016
@@ -177,8 +177,6 @@ persistent Apache Gora persistent dataSt
 <ul>
 <li><a href="#overview">Overview</a></li>
 <li><a href="#goraproperties">gora.properties</a></li>
-<li><a href="#overview_1">Overview</a></li>
-<li><a href="#goraproperties_1">gora.properties</a></li>
 </ul>
 </div>
 <h2 id="goraproperties">gora.properties<a class="headerlink" href="#goraproperties"
title="Permanent link">&para;</a></h2>
@@ -219,96 +217,6 @@ assigned value should be <b>org.apache.g
 </li>
 <li>
 <p><code>jcache.read.through.enable</code> - Whether to fetch a missing
cache entry from backend persistent dataStore. Default value is <b>true</b>.</p>
-</li>
-<li>
-<p><code>jcache.write.through.enable</code> - Whether to push change of
a cache entry to backend persistent dataStore. Default value is <b>true</b>.</p>
-</li>
-<li>
-<p><code>jcache.statistics.enable</code> - Statistics like cache hits and
misses are collected. Default value is <b>false</b>.</p>
-</li>
-<li>
-<p><code>jcache.management.enable</code> - JMX beans are enabled and collected
statistics are exposed over the beans.It doesn't automatically enables statistics collection.
-Default is set to false. Default JMX port opens on <b>9999</b>.</p>
-</li>
-<li>
-<p><code>jcache.store.by.value.enable</code> - Whether to store key and
values of data beans in means of store by value or store by reference. Default is <b>true</b>
that means store by <b>value</b>.</p>
-</li>
-<li>
-<p><code>jcache.cache.namespace</code> - Cache manager scope URI. This
will allow different cache manager instances to share data among them if they are aligned
with same scope.
-  On opposite having two different scopes means such that each cache manager can isolate
each other’s owned caches without any conflict. 
-  Please see <a href="http://docs.hazelcast.org/docs/3.5/manual/html/jcache-icache.html">Scopes
and Namespaces</a></p>
-</li>
-<li>
-<p><code>jcache.expire.policy</code> - Cache entry expiry policy. Possible
values <b> ACCESSED, CREATED, MODIFIED, TOUCHED </b>
-  Please see <a href="http://docs.hazelcast.org/docs/3.5/manual/html/jcache-expirepolicy.html">JCache
expiry policy</a></p>
-</li>
-<li>
-<p><code>jcache.expire.policy.duration</code> - Cache entry expiry timeout
in seconds.</p>
-</li>
-<li>
-<p><code>jcache.eviction.policy</code> - Cache entry eviction policy. Possible
values <b> LRU, LFU, NONE, RANDOM </b>
-  Please see <a href="http://docs.hazelcast.org/docs/3.5/manual/html/jcache-eviction.html">Hazelcast
eviction policy</a></p>
-</li>
-<li>
-<p><code>jcache.eviction.max.size.policy</code> - Measure of maximum cache
size to apply eviction policy. 
-  <b> ENTRY_COUNT, USED_NATIVE_MEMORY_SIZE, USED_NATIVE_MEMORY_PERCENTAGE, FREE_NATIVE_MEMORY_SIZE,
FREE_NATIVE_MEMORY_PERCENTAGE </b></p>
-</li>
-<li>
-<p><code>jcache.eviction.size</code> - Maximum size as integer as a measure
of max size policy criteria.
-Title: Gora JCache Module</p>
-</li>
-</ul>
-<h2 id="overview_1">Overview<a class="headerlink" href="#overview_1" title="Permanent
link">&para;</a></h2>
-<p>This is the main documentation for the gora-jcache module. gora-jcache
-module enables <a href="https://hazelcast.com/use-cases/caching/jcache-provider">Hazelcast
JCache</a> caching support for Gora.
-This implementation is based on Hazelcast JCache provider. This dataStore can act as wrapped
caching layer for any other 
-persistent Apache Gora persistent dataStore.</p>
-<div class="toc">
-<ul>
-<li><a href="#overview">Overview</a></li>
-<li><a href="#goraproperties">gora.properties</a></li>
-<li><a href="#overview_1">Overview</a></li>
-<li><a href="#goraproperties_1">gora.properties</a></li>
-</ul>
-</div>
-<h2 id="goraproperties_1">gora.properties<a class="headerlink" href="#goraproperties_1"
title="Permanent link">&para;</a></h2>
-<ul>
-<li>
-<p><code>gora.cache.datastore.default</code> - Caching dataStore to be
used with persistent dataStore. If JCache dataStore is used as caching store
-assigned value should be <b>org.apache.gora.jcache.store.JCacheStore</b> <code>(
Mandatory )</code></p>
-</li>
-<li>
-<p><code>gora.datastore.default</code> - Persistent back-end dataStore
to be used with JCache caching dataStore. <code>( Mandatory )</code></p>
-</li>
-<li>
-<p><code>gora.datastore.jcache.provider</code> - Two possible values, whether
to start JCache dataStore in Server mode or Client mode,</p>
-</li>
-<li>Server Mode
-     <b>com.hazelcast.cache.impl.HazelcastServerCachingProvider</b></li>
-<li>
-<p>Client Mode
-     <b>com.hazelcast.client.cache.impl.HazelcastClientCachingProvider</b>  <code>(
Mandatory )</code></p>
-</li>
-<li>
-<p><code>gora.datastore.jcache.hazelcast.config</code> - If JCache datastore
is started in,</p>
-</li>
-<li>Server Mode
-     This property to should point s to Hazelcast Cluster member network configuration file
related to
-     forming Hazelcast cluster using members. Please see <a href="http://docs.hazelcast.org/docs/3.5/manual/html/networkconfiguration.html">Network
configuration</a>.</li>
-<li>
-<p>Client Mode
-     This property to should point s to Hazelcast client configuration file related to connecting
related to already formed Hazelcast cluster.
-     Please see <a href="http://docs.hazelcast.org/docs/3.5/manual/html/javaclientconfiguration.html#java-client-configuration">Client
configuration</a>  <code>( Mandatory )</code></p>
-</li>
-<li>
-<p><code>jcache.auto.create.cache</code> - Whether force creating the cache
at time JCache dataStore creation. Default is set to <b>false</b>.</p>
-</li>
-<li>
-<p><code>jcache.cache.inmemory.format</code> - In memory for format for
persistent bean resides in cache. Possible values,
-  <b>BINARY, OBJECT, NATIVE</b> <a href="http://docs.hazelcast.org/docs/3.5/manual/html/map-inmemoryformat.html">In
memory format</a>.</p>
-</li>
-<li>
-<p><code>jcache.read.through.enable</code> - Whether to fetch a missing
cache entry from backend persistent dataStore. Default value is <b>true</b>.</p>
 </li>
 <li>
 <p><code>jcache.write.through.enable</code> - Whether to push change of
a cache entry to backend persistent dataStore. Default value is <b>true</b>.</p>



Mime
View raw message