Add support for expire after types: on-write, on-access #13
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit allows caches to be configured with an ExpireAfterType that controls how entries are expired from the cache; two types are supported. * ExpireAfterWrite specifies that each entry should be automatically removed from the cache once a fixed duration has elapsed after the entry's creation, or the most recent replacement of its value. * ExpireAfterAccess specifies that each entry should be automatically removed from the cache once a fixed duration has elapsed after the entry's creation, the most recent replacement of its value, or its last access. ExpireAfterType defaults to ExpireAfterWrite for backwards-compatibility. Signed-off-by: Daniel Ferstay <dferstay@splunk.com>
|
@calvinfo , @danielstjules , @rbranson , would you be able to take a look at this when you get a chance? :) Cheers, |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit allows caches to be configured with an ExpireAfterType that
controls how entries are expired from the cache; two types are supported.
removed from the cache once a fixed duration has elapsed after the
entry's creation, or the most recent replacement of its value.
removed from the cache once a fixed duration has elapsed after the
entry's creation, the most recent replacement of its value, or its last
access.
ExpireAfterType defaults to ExpireAfterWrite for backwards-compatibility.
Signed-off-by: Daniel Ferstay dferstay@splunk.com