You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Tommaso Teofili (JIRA)" <ji...@apache.org> on 2016/10/14 10:51:21 UTC
[jira] [Commented] (SLING-6054) JcrEventTrigger aggregation
resulting in unconsistent package
[ https://issues.apache.org/jira/browse/SLING-6054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15574959#comment-15574959 ]
Tommaso Teofili commented on SLING-6054:
----------------------------------------
fixed the previous issue in r1764869.
> JcrEventTrigger aggregation resulting in unconsistent package
> -------------------------------------------------------------
>
> Key: SLING-6054
> URL: https://issues.apache.org/jira/browse/SLING-6054
> Project: Sling
> Issue Type: Bug
> Components: Distribution
> Affects Versions: Content Distribution Core 0.1.18
> Reporter: Tommaso Teofili
> Assignee: Tommaso Teofili
> Fix For: Content Distribution 0.2.0
>
>
> {{JcrEventTrigger}} aggregates generated {{DistributionRequests}} in order to mitigate the risk of having badly ordered events result in distributions that may lead to unconsistent state of the receiving instance.
> In case 2 nodes one of which is descendant of the others get aggregated in the same request the resulting package will only include siblings of the deep path with its names, not their properties, resulting in removing existing properties by the deep node's siblings on the receiving side.
> I am not 100% sure this is a desired behaviour in FileVault, however since this may also affect custom serializers I think the right fix is to add the siblings's paths to such distribution requests.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)