Skip to content
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

[NEW] Support for HASH Eviction on basis of Keys & fields, Not only on KEY basis (for Client side caching) #1130

Closed
atharva29 opened this issue Oct 6, 2024 · 1 comment

Comments

@atharva29
Copy link

atharva29 commented Oct 6, 2024

The problem/use-case that the feature addresses

This will reduce the data transfer between client-side applications & valkey. (client side caching module)

Description of the feature

A description of what you want to happen.

Whenver there is a change in hash key. In client side caching, only the hash field of client side cache should be changed and should not update the whole hash key(with other fields). This will reduce the data transfer between client-side applications & valkey.

Alternatives you've considered
Currently whole Valkey hash key is cleared per hash field change. eg. If my key is user with fields id, address, designation. If I change only one field, the whole Valkey hash key shouldn't get cleared on the client side cache, only the field should be changed.
Solutions: We also need to add a field name in the keyspace notification.
redis/jedis#3987

Any alternative solutions or features you've considered, including references to existing open and closed feature requests in this repository.

Additional information

Any additional information that is relevant to the feature request.

@madolson
Copy link
Member

madolson commented Oct 6, 2024

Duplicate of #640. Feel free to move any additional context to this issue.

@madolson madolson closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants