-
Notifications
You must be signed in to change notification settings - Fork 8
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
Consider having a default spec that can be overruled per cache name #43
Comments
Hello @marceloverdijk , Thanks for your interest in my pet project, I'm happy that my idea is useful not only for me. Your suggestion looks cool. Most probably it's won't be used widely, but who cares? Also good point that you propose to name it I see just 2 possible items to consider:
But still, this is definitely a cool feature to add - feel free to contribute, or I'll handle it myself within this or next week. Cheers. |
GH-43: Introduce basic cache specification
Merged |
If the current implementation is already using Spring Boot's properties as default, then I do not understand what the original request is asking for. Why not use the spring boot's spring.cache.cache-names=cache1,cache2 as the base/default, and then just add coffee-boots.cache.spec.myCache=maximumSize=200000,expireAfterWrite=1m on top of that to override the default? What am I missing here? |
btw, I'd prefer to see the word "caffeine" to appear somewhere in the property name, just for clarity. e.g. coffee-boots.cache.caffeine.spec.myCache=.... |
I like to configure the caches via properties like:
For all caches I e.g. want
expireAfterWrite=1m
It would be nice to be able to specify a default spec like:
and then only overwrite the settings needed like:
The text was updated successfully, but these errors were encountered: