GitHub user emulvaney opened a pull request:
https://github.com/apache/storm/pull/501
An option for new/updated Redis keys to expire in RedisMapState
This is much the same as the mechanism already available via
`RedisStateUpdater` for `RedisState` instances. Users can now set
`expireIntervalSec` in their `RedisMapState.Options` instance, to set an expiry
timeout on each Redis key updated by the state.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/emulvaney/storm
feature/expire-in-redis-map-state
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/storm/pull/501.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #501
----
commit 52a7431ef35f54601c3ca80da3a3c5a787ec1f61
Author: eric-mulvaney <[email protected]>
Date: 2015-04-02T20:18:41Z
Made the keyFactory option public.
It can be set from the public API in other ways. Having it public
means we can set it along with other values like hkey.
commit 4a2ba19bd3577e081f7d007d7e42350a8d7c30ff
Author: eric-mulvaney <[email protected]>
Date: 2015-04-02T20:20:28Z
Added expireIntervalSec to RedisMapState.Options
This matches the option available to users of RedisStateUpdater.
Bit heavy when setting top-level keys, since Redis doesn't have
MSETEX to match its SETEX command where we could include an expiry
timeout. Pipelined to mitigate the overhead of needing to issue a
separate command per key.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
