[
https://issues.apache.org/jira/browse/OAK-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15028280#comment-15028280
]
Thomas Mueller commented on OAK-3646:
-------------------------------------
That sounds good to me. The RevisionComparator was my idea, and it was a bad
idea.
> It simply compares the revision with the revision vector to decide if the
> revision is visible or not.
Correct me if I'm wrong, the algorithm would be: for each revision in the
document, get the upper bound revision from the RevisionVector, and compare it.
Class name: what about RevisionHorizon? If it defines the line of what is
visible.
> 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)
