[MGNLADVCACHE-92] Support for explicit personalization (e.g. in an FTL) Created: 17/Jul/17 Updated: 11/Jul/19 |
|
| Status: | Open |
| Project: | Advanced Cache |
| Component/s: | personalization |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Description |
|
Problem: you can use p13n explicitly, without creating variants of components or pages. Advanced cache for p13n stores only UUID of variants as part of cache key. As result, only one cache item is stored for all three variants. Suggested solution: include all resolved variants into the cache key. (info.magnolia.personalization.decoration.cache.CachingPersonalizationContentDecorator component might be a good source of truth) |