[MGNLIMG-199] Cache can not be disabled anymore Created: 27/Jun/17  Updated: 19/Jul/17

Status: Open
Project: Imaging
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Marc Johnen Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
causality
caused by MGNLIMG-150 Extract Imaging entry point from Imag... Closed
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   

From version 3.3 on the property storeGeneratedImages is not being used anymore (see sourcecode), so the cache can't be disabled. It's not mentioned in the release notes.

Also the cache does not seem to be invalidated when exchanging images with the same path.

How to disable the cache?

As a bad surprise for us this had the effect, that after an upgrade images were delivered from the last time the cache was enabled about 2 years ago.



 Comments   
Comment by Philip Mundt [ 19/Jul/17 ]

Hi marc.johnen.

Thank you for reporting this issue.
As of version 3.3 this property was move to the module config config:/modules/imaging/config@storeGeneratedImages. It should be possible to disable the caching by adding the property to the config node and setting it to false.

This was indeed not mentioned in the release notes. I have asked our team to amend this information. Sorry for any inconviences.

Regards
Philip

Generated at Mon Feb 12 02:13:15 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.