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

Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2014/10/29 10:00:57 UTC

[jira] [Created] (SLING-4115) Optimise rename handling

Robert Munteanu created SLING-4115:
--------------------------------------

             Summary: Optimise rename handling
                 Key: SLING-4115
                 URL: https://issues.apache.org/jira/browse/SLING-4115
             Project: Sling
          Issue Type: Improvement
          Components: IDE
    Affects Versions: Sling Eclipse IDE 1.0.4
            Reporter: Robert Munteanu
            Priority: Minor
             Fix For: Sling Eclipse IDE 1.1.0


A rename operation is translated right now into a bulk delete ( see SLING-3607 for delete optimisations ) and a bulk add. If the rename is peformed for a resource with lots of children, this is very inefficient.

We should be able to detect such occurences and translate them into a single RenameOperation which, in case of the vlt-based implementation, delegates to Session#move(String, String) .



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)