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 2020/09/24 09:34:00 UTC

[jira] [Created] (OAK-9230) CachingCommitValueResolver with negative cache

Marcel Reutegger created OAK-9230:
-------------------------------------

             Summary: CachingCommitValueResolver with negative cache
                 Key: OAK-9230
                 URL: https://issues.apache.org/jira/browse/OAK-9230
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: documentmk
            Reporter: Marcel Reutegger
            Assignee: Marcel Reutegger


CachingCommitValueResolver currently only caches non-null commit values because a revision could be from an in-progress commit and currently does not have a commit value. Once the commit made it through, the commit value will be non-null.

For some use cases it would be beneficial to have a negative cache for revisions that are known to stay in the un-committed state. E.g. old branch commits that cannot be merged or old un-committed changes from inactive clusterIds.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)