[MGNLADVCACHE-69] EagerRecacheFlushPolicy only works for a cache named "default" Created: 04/Mar/16  Updated: 24/Mar/16  Resolved: 24/Mar/16

Status: Closed
Project: Advanced Cache
Component/s: core
Affects Version/s: 1.6
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Teresa Miyar Assignee: Roman Kovařík
Resolution: Won't Fix Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
dependency
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:

 Description   

To reproduce, set the eagerRecachePolicy advance cache settings, duplicate the default cache and rename to anything. Activate pages and check that they are not refreshed.

Problem seems to be on the extending of the AbstractSiteAwareListeningFlushPolicy it sets the observation to "mycachename/" as the path, even though I am not enabling site aware cache, just two different caches.



 Comments   
Comment by Roman Kovařík [ 24/Mar/16 ]

EagerRecacheFlushPolicy is site aware cache. That was always the case. You can't use two separate caches for the same site. Changing of this would require a major change of concept.
This will be improved in Advanced Cache 1.7.3 (Magnolia 5.4.6) which uses mapping in the site config to create paths for cache flushing or fallbacks to whole workspace if site config or mapping is not found.

Generated at Sun Feb 11 23:10:42 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.