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/29 07:55:00 UTC

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

     [ https://issues.apache.org/jira/browse/OAK-10313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Reutegger resolved OAK-10313.
------------------------------------
    Fix Version/s: 1.54.0
       Resolution: Fixed

Merged PR.

> 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
>             Fix For: 1.54.0
>
>
> 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)