You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Marcel Reutegger (Jira)" <ji...@apache.org> on 2023/06/19 14:36:00 UTC

[jira] [Commented] (OAK-10313) Identify revisions created by late-write scenario

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

Marcel Reutegger commented on OAK-10313:
----------------------------------------

Created new tests in WriteAfterRecoveryTest similar to those in OAK-10254, but using the existing FailingDocumentStore (with some enhancements) to simulate 'late-write' scenarios for various content changes. The consistency check takes a root node state and a NodeDocument and identifies change revisions that are not visible when traversing to the node state represented by the given NodeDocument even though they should be given the head revision on the root node state.

Proposed changed in https://github.com/apache/jackrabbit-oak/pull/995

> Identify revisions created by late-write scenario
> -------------------------------------------------
>
>                 Key: OAK-10313
>                 URL: https://issues.apache.org/jira/browse/OAK-10313
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: documentmk, run
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>
> OAK-10254 describes a 'late-write' scenario where a DocumentNodeStore is writing some changes after its lease timed out.
> Introduce a consistency check that identifies those revisions on a NodeDocument.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)