[MAGNOLIA-6278] Files added at the same time as their parent directory are not loaded Created: 30/Jun/15  Updated: 21/Nov/16  Resolved: 26/Feb/16

Status: Closed
Project: Magnolia
Component/s: configuration
Affects Version/s: 5.4
Fix Version/s: 5.4.5

Type: Bug Priority: Major
Reporter: Christopher Zimmermann Assignee: Ilgun Ilgun
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 3d 1h
Original Estimate: 3d

Issue Links:
Relates
relates to MGNLCI-15 Dropping Folders under observed direc... Closed
causality
is causing MGNLCAMPU-55 Add to campaign default is blank used... Closed
is causing MAGNOLIA-6611 Relativize paths for deleted resource... Closed
relation
is related to MAGNOLIA-6223 Provide proper API for resource chang... 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
Epic Link: Resource reloading without restart
Sprint: Basel 33
Story Points: 5

 Description   

Problem

When one moves a folder with some files inside, to another path, then DirectoryWatcher do not pick up those changes (files are not recognized). It is happening due to the fact that we only receive event for the folder change, but , not the files under the given folder.

Solution

It had been clear after the investigation which is documented in https://wiki.magnolia-cms.com/display/DEV/Filesystem+observation+overview+on+various+platforms that, we do not get CREATE event for added folder, and hence, we should be traversing it explicitly. Afterwards, we will have the updated information and hence, AbstractFileResourceConfigurationSource and thus Registry will not have stale information.



 Comments   
Comment by Christopher Zimmermann [ 31/Aug/15 ]

Ranking this high because this can cause confusion and frustration with config by file - as well as slowing down development by requiring a restart.
Parent ticket may need to be addressed to fix this issue.

Generated at Mon Feb 12 04:12:59 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.