-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Duplicate
-
Affects Version/s: 3.2 Enterprise
-
Fix Version/s: 3.4.a Community
-
Component/s: Repository
-
Labels:None
With the refactoring of the content URL storage and attendant performance improvements, any old-style ContentData storage will be left behind. The side-effect of this is that the orphaned content will not be cleaned up if it is deleted without archival or any other metadata change; in DM, a metadata change will automatically do the job, but this is not true for AVM.
The migration for DM should run during a pass of the ContentStore cleaner and touch the metadata properties to trigger the migration. AVM can lazily do it in the OrphanReaper.