[MGNLCACHE-83] Implement CacheKeyGenerator Created: 05/Feb/15 Updated: 25/May/15 Resolved: 19/Feb/15 |
|
| Status: | Closed |
| Project: | Cache Modules |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
||||||||||||
| Date of First Response: | |||||||||||||
| Epic Link: | DPC | ||||||||||||
| Description |
|
Allow to use a custom CacheKey/CacheKeyGenerator per cache policy. |
| Comments |
| Comment by Jan Haderka [ 19/Feb/15 ] |
|
DefaultCacheKey.hashcode()
I would also argue that as a key cache key should be immutable. First it's good practice, second it does wonders for object allocation in memory of VM Default |