[OAK-4853] User defined property values in event info

• Type: New Feature
• Status: Resolved
• Priority: Major
• Resolution: Won't Fix
• Component/s: jcr
• Labels: observation
• Epic Link: Improve observation resilience
• Assignee: Unassigned
• Reporter: Marcel Reutegger
• Created: 27/Sep/16 09:01
• Updated: 02/Nov/16 11:18
• Resolved: 02/Nov/16 11:18

Description

An event listener should be able to define a set of names of properties available in the info map of node events. This allows a listener to more efficiently process events, because it does not have to resolve the event path into a JCR item anymore. It would simply read the values of those properties from the event info map.

A similar feature was already implemented for property events: OAK-2262. However, there are also listeners that are interested in properties that did not change. One such application is Apache Sling, which heavily depends on properties like sling:resourceType. In many cases listener logic depends on the resource type and needs to know this value even if it didn't change.

Issue Links

• blocks: SLING-6070 Reduce temporary storage required in JcrResourceListener, call reportChanges earlier
• relates to: OAK-4581 Persistent local journal for more reliable event generation