You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Bryan Bende (JIRA)" <ji...@apache.org> on 2018/05/23 19:31:00 UTC

[jira] [Resolved] (NIFI-4987) Support TTL in Redis

     [ https://issues.apache.org/jira/browse/NIFI-4987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bryan Bende resolved NIFI-4987.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.7.0

> 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
>             Fix For: 1.7.0
>
>
> 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)