[
https://issues.apache.org/jira/browse/NIFI-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16487899#comment-16487899
]
ASF subversion and git services commented on NIFI-4987:
-------------------------------------------------------
Commit 06d45c3a6ea30c5dc51d5f320d423dafc10271f8 in nifi's branch
refs/heads/master from [~sivaprasanna]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=06d45c3 ]
NIFI-4987: Added TTL to RedisDistributedMapCacheClientService
NIFI-4987: PR Review Fixes - Reverted getAndPutIfAbsent and added TTL setting
with a different approach
NIFI-4987: PR Review Fixes - Added TTL to putIfAbsent()
This closes #2726.
Signed-off-by: Bryan Bende <[email protected]>
> Support TTL in Redis
> --------------------
>
> Key: NIFI-4987
> URL: https://issues.apache.org/jira/browse/NIFI-4987
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Brian Ghigiarelli
> Assignee: Sivaprasanna Sethuraman
> Priority: Minor
>
> To properly integrate the NiFi with Redis, it would be nice to support
> setting TTLs for keys, whether a global TTL is used for the particular Redis
> database, or a configurable TTL is used for each key. At the moment, the
> PutDistributedMapCache processor that uses the
> RedisDistributedMapCacheClientService and calls to the
> RedisConnectionPoolService does not pass in any TTL / EXPIRE parameter, so
> Redis will cache the value potentially forever unless Redis itself clears the
> key based on its configured maxmemory eviction strategy.
> On
> [SO|https://stackoverflow.com/questions/49321005/setting-ttl-on-redis-with-apache-nifi-putdistributedmapcache/49324205#49324205],
> [~bbende] suggested either a PutRedis processor or a modification to the
> RedisDistributedMapCacheClientService.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
