[
https://issues.apache.org/jira/browse/SLING-1747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved SLING-1747.
-------------------------------------
Resolution: Won't Fix
We can't avoid the copying as the installer needs symbolic name and version to
check if the resource has been commtted on previous attempts. As this
information is inside the data, we have to read from the input stream anyway.
Setting to won't fix.
> Don't copy already installed resources
> --------------------------------------
>
> Key: SLING-1747
> URL: https://issues.apache.org/jira/browse/SLING-1747
> Project: Sling
> Issue Type: Improvement
> Components: Installer
> Affects Versions: OSGi Installer 3.0.0
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Fix For: OSGi Installer 3.0.0
>
>
> Currently during the rendezvous of the osgi installer and a client (e.g. jcr
> install) jcr install sends all available resources which are then first
> processed by the osgi installer by creating local copies. In a second (async)
> step, these new resources are compared with available ones and if already
> available discarded.
> With larger installation this becomes very disc intensive and slow as each
> bundle is copied over on startup just to be deleted in the second step.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
