[ https://issues.apache.org/jira/browse/SLING-5371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15052850#comment-15052850 ]
Carsten Ziegeler commented on SLING-5371: ----------------------------------------- So far the JCR Installer uses plain JCR API - this patch requires special API outside the spec. The patch is also using a 2.7.5-rXXX dependency which is not available in a public Maven repo > Improving JcrInstaller's move listener registration > --------------------------------------------------- > > Key: SLING-5371 > URL: https://issues.apache.org/jira/browse/SLING-5371 > Project: Sling > Issue Type: Improvement > Components: Installer > Reporter: Marc Pfaff > Attachments: SLING_5371.patch > > > The JcrInstaller is currently registering a JCR listener for move events on > the root node with setting the 'deep' property to true. If it comes to > processing the underlaying Oak observation queue, this combination is very > inefficient, as it does not allow Oak to filter changes by path. > AFAIU this move listener is covering the use case where an installer artifact > is moved from/to an installer root folder. I therefore wanted to propose to > register the move listener on the configured root folders only. -- This message was sent by Atlassian JIRA (v6.3.4#6332)