Chetan Mehrotra commented on OAK-4586:

Another thing to collect is node names whose properties got modified 
(changed/added/deleted node). This would be useful for certain types of 

/cc [~cziegeler]

> Collect affected node types on commit
> -------------------------------------
>                 Key: OAK-4586
>                 URL: https://issues.apache.org/jira/browse/OAK-4586
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: jcr
>            Reporter: Marcel Reutegger
>              Labels: observation
> One of the major optimizations for generating events in oak-jcr is to avoid 
> traversal into sub trees when there are path filters on an observation 
> listener. Another optimization could be done based on the node type filters 
> provided by a listener. If oak-jcr knows the affected node types of a cache 
> set it could shortcut event processing in case the listeners node type filter 
> is disjoint.

This message was sent by Atlassian JIRA

Reply via email to