You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/09/19 13:58:20 UTC

[jira] [Commented] (OAK-4586) Collect affected node types on commit

    [ https://issues.apache.org/jira/browse/OAK-4586?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503565#comment-15503565 ] 

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 [listeners|http://markmail.org/thread/diixjz6eoipilwf7]

/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
(v6.3.4#6332)