camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CAMEL-9023) Use Redis String instead of Set as datatype for idempotent consumer
Date Fri, 25 Sep 2015 09:21:05 GMT

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

Claus Ibsen resolved CAMEL-9023.
--------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s:     (was: Future)
                   2.16.0

> 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
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.16.0
>
>
> 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)

Mime
View raw message