org.apache.nifinifi-redis-nar2.4.0org.apache.nifinifi-redis-service-api-nar2.4.02.1.0rel/nifi-2.4.0main1org.apache.nifi.redis.processor.PutRedisHashRecordPROCESSORPuts record field data into Redis using a specified hash value, which is determined by a RecordPath to a field in each record containing the hash value. The record fields and values are stored as key/value pairs associated by the hash value. NOTE: Neither the evaluated hash value nor any of the field values can be null. If the hash value is null, the FlowFile will be routed to failure. For each of the field values, if the value is null that field will be not set in Redis.putredishashrecordrecord-readerRecord ReaderSpecifies the Controller Service to use for parsing incoming data and determining the data's schemaorg.apache.nifi.serialization.RecordReaderFactoryorg.apache.nifinifi-standard-services-api-nar2.4.0truefalsefalseNONEfalsefalseredis-connection-poolRedis Connection Poolorg.apache.nifi.redis.RedisConnectionPoolorg.apache.nifinifi-redis-service-api-nar2.4.0truefalsefalseNONEfalsefalsehash-value-record-pathHash Value Record PathSpecifies a RecordPath to evaluate against each Record in order to determine the hash value associated with all the record fields/values (see 'hset' in Redis documentation for more details). The RecordPath must point at exactly one field or an error will occur.truefalsefalseNONEfalsefalsedata-record-pathData Record PathThis property denotes a RecordPath that will be evaluated against each incoming Record and the Record that results from evaluating the RecordPath will be sent to Redis instead of sending the entire incoming Record. The property defaults to the root '/' which corresponds to a 'flat' record (all fields/values at the top level of the Record./truefalsefalseNONEfalsefalsecharsetCharacter SetSpecifies the character set to use when storing record field values as strings. All fields will be converted to strings using this character set before being stored in Redis.UTF-8truefalsetrueFLOWFILE_ATTRIBUTESfalsefalsefailureFlowFiles containing Records with processing errors will be routed to this relationshipfalsesuccessFlowFiles having all Records stored in Redis will be routed to this relationshipfalseredis.success.record.countNumber of records written to RedisINPUT_REQUIREDorg.apache.nifi.redis.service.RedisConnectionPoolServiceCONTROLLER_SERVICEA service that provides connections to Redis.rediscacheRedis ModeRedis ModeThe type of Redis being communicated with - standalone, sentinel, or clustered.StandaloneStandaloneStandaloneA single standalone Redis instance.SentinelSentinelRedis Sentinel which provides high-availability. Described further at https://redis.io/topics/sentinelClusterClusterClustered Redis which provides sharding and replication. Described further at https://redis.io/topics/cluster-spectruefalsefalseNONEfalsefalseConnection StringConnection StringThe connection string for Redis. In a standalone instance this value will be of the form hostname:port. In a sentinel instance this value will be the comma-separated list of sentinels, such as host1:port1,host2:port2,host3:port3. In a clustered instance this value will be the comma-separated list of cluster masters, such as host1:port,host2:port,host3:port.truefalsetrueENVIRONMENTfalsefalseDatabase IndexDatabase IndexThe database index to be used by connections created from this connection pool. See the databases property in redis.conf, by default databases 0-15 will be available.0truefalsetrueENVIRONMENTfalsefalseCommunication TimeoutCommunication TimeoutThe timeout to use when attempting to communicate with Redis.10 secondstruefalsefalseNONEfalsefalseCluster Max RedirectsCluster Max RedirectsThe maximum number of redirects that can be performed when clustered.5truefalsefalseNONEfalsefalseSentinel MasterSentinel MasterThe name of the sentinel master, require when Mode is set to SentinelfalsefalsetrueENVIRONMENTfalsefalseUsernameUsernameThe username used to authenticate to the Redis server.falsefalsetrueENVIRONMENTfalsefalsePasswordPasswordThe password used to authenticate to the Redis server. See the 'requirepass' property in redis.conf.falsetruetrueENVIRONMENTfalsefalseSentinel UsernameSentinel UsernameThe username used to authenticate to the Redis sentinel server.falsefalsetrueENVIRONMENTfalsefalseSentinel PasswordSentinel PasswordThe password used to authenticate to the Redis Sentinel server. See the 'requirepass' and 'sentinel sentinel-pass' properties in sentinel.conf.falsetruetrueENVIRONMENTfalsefalseSSL Context ServiceSSL Context ServiceIf specified, this service will be used to create an SSL Context that will be used to secure communications; if not specified, communications will not be secureorg.apache.nifi.ssl.SSLContextProviderorg.apache.nifinifi-standard-services-api-nar2.4.0falsefalsefalseNONEfalsefalsePool - Max TotalPool - Max TotalThe maximum number of connections that can be allocated by the pool (checked out to clients, or idle awaiting checkout). A negative value indicates that there is no limit.8truefalsefalseNONEfalsefalsePool - Max IdlePool - Max IdleThe maximum number of idle connections that can be held in the pool, or a negative value if there is no limit.8truefalsefalseNONEfalsefalsePool - Min IdlePool - Min IdleThe target for the minimum number of idle connections to maintain in the pool. If the configured value of Min Idle is greater than the configured value for Max Idle, then the value of Max Idle will be used instead.0truefalsefalseNONEfalsefalsePool - Block When ExhaustedPool - Block When ExhaustedWhether or not clients should block and wait when trying to obtain a connection from the pool when the pool has no available connections. Setting this to false means an error will occur immediately when a client requests a connection and none are available.truetruetruefalsefalsetruefalsefalseNONEfalsefalsePool - Max Wait TimePool - Max Wait TimeThe amount of time to wait for an available connection when Block When Exhausted is set to true.10 secondstruefalsefalseNONEfalsefalsePool - Min Evictable Idle TimePool - Min Evictable Idle TimeThe minimum amount of time an object may sit idle in the pool before it is eligible for eviction.60 secondstruefalsefalseNONEfalsefalsePool - Time Between Eviction RunsPool - Time Between Eviction RunsThe amount of time between attempting to evict idle connections from the pool.30 secondstruefalsefalseNONEfalsefalsePool - Num Tests Per Eviction RunPool - Num Tests Per Eviction RunThe number of connections to tests per eviction attempt. A negative value indicates to test all connections.-1truefalsefalseNONEfalsefalsePool - Test On CreatePool - Test On CreateWhether or not connections should be tested upon creation.falsetruetruefalsefalsetruefalsefalseNONEfalsefalsePool - Test On BorrowPool - Test On BorrowWhether or not connections should be tested upon borrowing from the pool.falsetruetruefalsefalsetruefalsefalseNONEfalsefalsePool - Test On ReturnPool - Test On ReturnWhether or not connections should be tested upon returning to the pool.falsetruetruefalsefalsetruefalsefalseNONEfalsefalsePool - Test While IdlePool - Test While IdleWhether or not connections should be tested while idle.truetruetruefalsefalsetruefalsefalseNONEfalsefalseorg.apache.nifi.redis.RedisConnectionPoolorg.apache.nifinifi-redis-service-api-nar2.4.0org.apache.nifi.redis.service.RedisDistributedMapCacheClientServiceCONTROLLER_SERVICEAn implementation of DistributedMapCacheClient that uses Redis as the backing cache. This service relies on the WATCH, MULTI, and EXEC commands in Redis, which are not fully supported when Redis is clustered. As a result, this service can only be used with a Redis Connection Pool that is configured for standalone or sentinel mode. Sentinel mode can be used to provide high-availability configurations.redisdistributedcachemapredis-connection-poolRedis Connection Poolorg.apache.nifi.redis.RedisConnectionPoolorg.apache.nifinifi-redis-service-api-nar2.4.0truefalsefalseNONEfalsefalseredis-cache-ttlTTLIndicates how long the data should exist in Redis. Setting '0 secs' would mean the data would exist forever0 secstruefalsefalseNONEfalsefalseorg.apache.nifi.distributed.cache.client.AtomicDistributedMapCacheClientorg.apache.nifinifi-standard-services-api-nar2.4.0org.apache.nifi.distributed.cache.client.DistributedMapCacheClientorg.apache.nifinifi-standard-services-api-nar2.4.0org.apache.nifi.redis.service.SimpleRedisDistributedMapCacheClientServiceCONTROLLER_SERVICEAn implementation of DistributedMapCacheClient that uses Redis as the backing cache. This service is intended to be used when a non-atomic DistributedMapCacheClient is required.redisdistributedcachemapredis-connection-poolRedis Connection Poolorg.apache.nifi.redis.RedisConnectionPoolorg.apache.nifinifi-redis-service-api-nar2.4.0truefalsefalseNONEfalsefalseredis-cache-ttlTTLIndicates how long the data should exist in Redis. Setting '0 secs' would mean the data would exist forever0 secstruefalsefalseNONEfalsefalseorg.apache.nifi.distributed.cache.client.DistributedMapCacheClientorg.apache.nifinifi-standard-services-api-nar2.4.0