[
https://issues.apache.org/jira/browse/SLING-4115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-4115:
-----------------------------------
Fix Version/s: Sling Eclipse IDE 2.0.2
Sling Eclipse IDE 2.0.2
(was: Sling Eclipse IDE 2.0.0)
> 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 2.0.2
>
>
> 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
(v8.20.10#820010)
