| <!DOCTYPE html><html lang="en"><head><meta charset="utf-8"></meta><title>HazelcastMapCacheClient</title><link rel="stylesheet" href="../../../../../css/component-usage.css" type="text/css"></link></head><script type="text/javascript">window.onload = function(){if(self==top) { document.getElementById('nameHeader').style.display = "inherit"; } }</script><body><h1 id="nameHeader" style="display: none;">HazelcastMapCacheClient</h1><h2>Description: </h2><p>An implementation of DistributedMapCacheClient that uses Hazelcast as the backing cache. This service relies on an other controller service, manages the actual Hazelcast calls, set in Hazelcast Cache Manager.</p><p><a href="additionalDetails.html">Additional Details...</a></p><h3>Tags: </h3><p>hazelcast, cache, map</p><h3>Properties: </h3><p>In the list below, the names of required properties appear in <strong>bold</strong>. Any other properties (not in bold) are considered optional. The table also indicates any default values, and whether a property supports the <a href="../../../../../html/expression-language-guide.html">NiFi Expression Language</a>.</p><table id="properties"><tr><th>Display Name</th><th>API Name</th><th>Default Value</th><th>Allowable Values</th><th>Description</th></tr><tr><td id="name"><strong>Hazelcast Cache Manager</strong></td><td>hazelcast-cache-manager</td><td></td><td id="allowable-values"><strong>Controller Service API: </strong><br/>HazelcastCacheManager<br/><strong>Implementations: </strong><a href="../org.apache.nifi.hazelcast.services.cachemanager.ExternalHazelcastCacheManager/index.html">ExternalHazelcastCacheManager</a><br/><a href="../org.apache.nifi.hazelcast.services.cachemanager.EmbeddedHazelcastCacheManager/index.html">EmbeddedHazelcastCacheManager</a></td><td id="description">A Hazelcast Cache Manager which manages connections to Hazelcast and provides cache instances.</td></tr><tr><td id="name"><strong>Hazelcast Cache Name</strong></td><td>hazelcast-cache-name</td><td></td><td id="allowable-values"></td><td id="description">The name of a given cache. A Hazelcast cluster may handle multiple independent caches, each identified by a name. Clients using caches with the same name are working on the same data structure within Hazelcast.<br/><strong>Supports Expression Language: true (will be evaluated using variable registry only)</strong></td></tr><tr><td id="name"><strong>Hazelcast Entry Lifetime</strong></td><td>hazelcast-entry-ttl</td><td id="default-value">0 secs</td><td id="allowable-values"></td><td id="description">Indicates how long the written entries should exist in Hazelcast. Setting it to '0 secs' means that the datawill exists until its deletion or until the Hazelcast server is shut down.</td></tr></table><h3>State management: </h3>This component does not store state.<h3>Restricted: </h3>This component is not restricted.<h3>System Resource Considerations:</h3>None specified.</body></html> |