[
https://issues.apache.org/jira/browse/OAK-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028698#comment-15028698
]
Marcel Reutegger commented on OAK-3646:
---------------------------------------
The name RevisionVector is inspired by [Version
Vectors|https://en.wikipedia.org/wiki/Version_vector]. A revision vector works
very similar to a version vector. The third update rule is a bit different with
revision vectors, because a revision is bound to the local clock. In Oak the
third rule is implemented by OAK-3388 where the background read waits until the
local clock is passed the most recent reported external _lastRev and the
timestamp of the new head revision is therefore newer than the timestamps of
the most recent visible external revisions.
> Inconsistent read of hierarchy
> -------------------------------
>
> Key: OAK-3646
> URL: https://issues.apache.org/jira/browse/OAK-3646
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core, documentmk
> Affects Versions: 1.0, 1.2
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Fix For: 1.4
>
>
> This is similar to OAK-3388, but about hierarchy information like which child
> nodes exist at a given revision of the parent node. This issue only occurs in
> a cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
