You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/29 12:39:04 UTC

[jira] [Updated] (CAMEL-9023) Use Redis String instead of Set as datatype for idempotent consumer

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

Claus Ibsen updated CAMEL-9023:
-------------------------------
    Fix Version/s: Future

> Use Redis String instead of Set as datatype for idempotent consumer
> -------------------------------------------------------------------
>
>                 Key: CAMEL-9023
>                 URL: https://issues.apache.org/jira/browse/CAMEL-9023
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-spring-redis
>    Affects Versions: 2.15.2
>            Reporter: Marco Zapletal
>            Priority: Minor
>             Fix For: Future
>
>
> The current implementation of the RedisIdempotentRepository uses a (Redis) set as the underlying data structure. This is conceptually nice for keeping all consumed keys in a single logical location. However, it makes the management of keys more difficult, since we cannot use Redis' built in mechanisms for expiring keys and have to do a manual cleanup.
> Thus, this issue proposes to use Redis String as the datatype for a single entry in order to provide support for expiring keys. If the community is in favor of this idea, I am happy to provide a patch (or a second, alternative implementation).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)