[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nicolas Peltier updated SLING-4797: --- Fix Version/s: (was: Content Distribution Core 0.3.0) > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus >Priority: Major > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Tripodi updated SLING-4797: -- Fix Version/s: (was: Content Distribution Core 0.2.10) Content Distribution Core 0.2.12 > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > Fix For: Content Distribution Core 0.2.12 > > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-4797: -- Fix Version/s: (was: Content Distribution Core 0.2.6) Content Distribution Core 0.2.8 > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > Fix For: Content Distribution Core 0.2.8 > > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-4797: -- Fix Version/s: (was: Content Distribution Core 0.2.4) Content Distribution Core 0.2.6 > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > Fix For: Content Distribution Core 0.2.6 > > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Timothee Maret updated SLING-4797: -- Fix Version/s: (was: Content Distribution Core 0.2.0) Content Distribution Core 0.2.2 > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Content Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > Fix For: Content Distribution Core 0.2.2 > > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tommaso Teofili updated SLING-4797: --- Fix Version/s: Content Distribution 0.2.0 > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > Fix For: Content Distribution 0.2.0 > > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4797) Improve handling of Move events
[ https://issues.apache.org/jira/browse/SLING-4797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konrad Windszus updated SLING-4797: --- Description: In case you are moving a node with a lot of subnodes, this leads to a distributed deletion of the node, followed by the distributed addition of the node with all subnodes. To improve the performance it would be good, if the move operation would really be distributed through a move event, which means that each receiver would try to move the node (instead of first deleting it and then adding it with all its subnodes). was: In case you are moving a node with a lot of subnodes, this leads to a distributed deletion of the node, followed by the distributed addition of the node with all subnodes. To improve the performance it would be good, if the move operation would really by distributed by a move event, which means that each receiver would try to move the node (instead of first deleting it and then adding it with all its subnodes). > Improve handling of Move events > --- > > Key: SLING-4797 > URL: https://issues.apache.org/jira/browse/SLING-4797 > Project: Sling > Issue Type: Improvement > Components: Distribution >Affects Versions: Content Distribution Core 0.1.4 >Reporter: Konrad Windszus > > In case you are moving a node with a lot of subnodes, this leads to a > distributed deletion of the node, followed by the distributed addition of the > node with all subnodes. > To improve the performance it would be good, if the move operation would > really be distributed through a move event, which means that each receiver > would try to move the node (instead of first deleting it and then adding it > with all its subnodes). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
