-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature to provide Event of KEY's data which is Altered/changed in Server Assisted Client Side Caching module #4040
Comments
@atharva29 When enabling server assisted client side caching, you can pass an implementation of You can override our |
Hi @sazzad16 , I’ve implemented a custom Cache and used the deleteByRedisKey and deleteByRedisKeys methods as you recommended. However, I noticed that the invalidated keys are only being logged when a GET request is made for the key, instead of immediately upon the key's data being altered or invalidated. I have made the changes in the redis database manually for that key that i have already in my cache but i am not getting key printing in my console. the deleteByRedisKey and deleteByRedisKeys are triggered when i made get request to them. below is my code that i have developed This is CustomCache class which extends AbstractCache ` import redis.clients.jedis.csc.AbstractCache; public class CustomCache extends AbstractCache {
}` This is RedisConfig class which uses CustomCache ` import java.util.Collection; @configuration
}` This is RedisController class for making request to redis database ` import org.springframework.beans.factory.annotation.Autowired; @RestController
}` |
By design, it may take as much as next command in the same Connection or on the same key for the cache to be updated. So it is by design, you don't get the following:
|
##Feature to provide Event of KEY's Name which is Altered/changed in Server Assisted Client Side Caching module
Expected behavior
I should get value/data of Key which is changed or altered. By adding this feature, client can prefetch the changed value and update its cache. We can enable this feature using a simple flag, such that if required user can enable this.
Write here what you're expecting ...
Actual behavior
Currently jedis invalidates that changed key & doesn't provide the key's name
Redis / Jedis Configuration
Jedis version:
v5.2.0
Redis version:
7.4.1
Java version:
The text was updated successfully, but these errors were encountered: