[MGNLADVCACHE-66] Site aware cache could retrieve mappings from site definitions which would simplifying configuration Created: 11/Jan/16 Updated: 18/May/16 Resolved: 24/Mar/16 |
|
| Status: | Closed |
| Project: | Advanced Cache |
| Component/s: | core |
| Affects Version/s: | 1.7 |
| Fix Version/s: | 1.7.3 |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Rico Jansen | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Centos 7 |
||
| 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)
|
||||||||||||||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||
| Visible to: |
Mathijn Elhorst, Michiel Meeuwissen, Nils Breunese
|
||||||||||||||||||||
| Sprint: | Kromeriz 36 | ||||||||||||||||||||
| Story Points: | 3 | ||||||||||||||||||||
| Description |
|
The advanced caching module creates several caches when 'createSeparateCachesForEachSite' is set. Each cache is created with the name of the site definition. When caching the info.magnolia.module.advancedcache.filter.SiteAwareCacheFilter takes care of storing and serving the content in the corresponding site cache. However the info.magnolia.module.advancedcache.SiteAwareFlushAllListeningPolicy which This breaks flushing in our case because of two reasons:
A second problem we don't encounter in our case is the fact that there is no discrimination between workspaces for the path. So the multisite content needs to live a the same place in all workspaces that are multisite aware. It would be better if the FlushPolicy used the sitedefinition and its repository mappings to register the correct path and workspace to observe. |