[jira] [Commented] (OAK-1182) incorrect order of remove, move & add events for a move operation

["Michael Dürig (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OAK-1182?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13822266#comment-13822266 ] 

Michael Dürig commented on OAK-1182:
------------------------------------

Applications should not rely on event ordering. The specification is [very clear | http://www.day.com/specs/jcr/2.0/12_Observation.html#12.4.1%20Event%20Ordering] on this.

There is nothing in Oak that guarantees {{NODE_MOVED}} events to occur before {{NODE_REMOVED}}. See the [Oak documentation | http://jackrabbit.apache.org/oak/docs/differences.html] for further information on how Oak observation works. 



> incorrect order of remove, move & add events for a move operation
> -----------------------------------------------------------------
>
>                 Key: OAK-1182
>                 URL: https://issues.apache.org/jira/browse/OAK-1182
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: jcr
>            Reporter: Ankush Malhotra
>              Labels: observation
>
> with jackrabbit2 move operation would cause three events - NODE_REMOVED, NODE_ADDED & NODE_MOVED - in this order. The order has changed recently with NODE_MOVED occurring before NODE_REMOVED. Not sure about NODE_ADDED since the code which broke was listening for only move & remove events.
> This would impact application which were dependent on order of these events. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)