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

Marcel Reutegger resolved OAK-9230.
-----------------------------------
    Fix Version/s: 1.36.0
       Resolution: Fixed

Applied changes in PR with minor modifications to trunk: 
http://svn.apache.org/r1881984

> 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
>            Priority: Minor
>             Fix For: 1.36.0
>
>
> 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)

Reply via email to