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 "Julian Reschke (Jira)" <ji...@apache.org> on 2026/03/05 20:24:00 UTC

[jira] [Comment Edited] (OAK-12128) Fail early when detecting late writes

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

Julian Reschke edited comment on OAK-12128 at 3/5/26 8:23 PM:
--------------------------------------------------------------

(working on a prototype in https://github.com/apache/jackrabbit-oak/tree/OAK-12128)


was (Author: reschke):
(working on a prototype)

> Fail early when detecting late writes
> -------------------------------------
>
>                 Key: OAK-12128
>                 URL: https://issues.apache.org/jira/browse/OAK-12128
>             Project: Jackrabbit Oak
>          Issue Type: Task
>          Components: documentmk
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>            Priority: Major
>
> While discussing late write with [~stefanegli] we realized that late writes (or at least some of them) can actually be detected in LeaseCheckDocumentStoreWrapper - if a write call completes *after* the lease check has expired, it is (likely) a late write and we can either make it fail, or at least log it.



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