[
https://issues.apache.org/jira/browse/OAK-1281?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger resolved OAK-1281.
-----------------------------------
Resolution: Fixed
Fix Version/s: 0.14
Fixed in http://svn.apache.org/r1550377
> Incorrect path sorting in background write
> ------------------------------------------
>
> Key: OAK-1281
> URL: https://issues.apache.org/jira/browse/OAK-1281
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, mongomk
> Affects Versions: 0.13
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Priority: Minor
> Fix For: 0.14
>
>
> The background write in MongoNodeStore does not sort path correctly. It is
> supposed to sort them with highest path depth first and then compare the path
> string itself (as written in the comments).
> A typo in the comparator implementation causes a differnt order than intended
> (depth is calculated twice for o1).
> In addition, there's a problem with the way MongoNodeStore updates the
> _lastRev. It may use a multi update and the order these updates are applied
> is not specified. Thus, it may happen that the root document is updated
> before other documents are updated. This may result in temporarily
> inconsistent _lastRev entries in the document hierarchy. I.e. a cluster node
> detects a _lastRev update from another cluster node on the root document, but
> on descendant documents the _lastRev isn't updated and visible yet.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
