[SLING-3505] Improve handling of updates to mapping (alias, vanity path)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: Resource Resolver 1.1.0
• Fix Version/s: Resource Resolver 1.1.2
• Component/s: ResourceResolver
• Assignee: Antonio Sanso
• Reporter: Carsten Ziegeler
• Created: 17/Apr/14 13:07
• Updated: 16/Sep/14 13:59
• Resolved: 01/Jul/14 09:26

Description

The update handling for the mapping including aliases and vanity path is a simple algorithm which simply updates the whole mapping. Especially with large mapping info spread across the repository, a simple update of a single property results in the whole mapping info to be recreated.
It would be great if this could be improved.
Right now, only the active mapping is hold in memory - as a change of a single property might cause to activate a totally different mapping than the one which was changed (e.h. when the ordering is changed), the update needs to be more complex or more information needs to be hold in memory.
In addition there is more to consider, like if the vanity path info is changed, only the new value is available - but the old is gone.

Issue Links

• blocks: SLING-3558 Updating of sling:VanityPath mixins is ignored by sling resource resolution
• blocks: SLING-3563 Removal of node with sling:alias property is ignored by sling resource resolution
• is related to: SLING-3692 Provide access to list of vanity paths/aliases in SLING-3505
• relates to: SLING-3706 Sling Resource Resolver - NPE with oak for vanity paths