Tommaso Teofili reopened SLING-6054:

reopening as the previous fix works or not depending on the order of the 
incoming {{DistributionRequests}}.

> 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

Reply via email to