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 "Vikas Saurabh (JIRA)" <ji...@apache.org> on 2018/03/16 10:25:00 UTC

[jira] [Commented] (OAK-6351) Invalidate cache entries when getChildNodes() is aborted

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

Vikas Saurabh commented on OAK-6351:
------------------------------------

[~mreutegg], I think we missed setting fix version = 1.2.27 here. Should we now set an unreleased version to have it show up in change log OR set it to 1.2.27 but not show up in change log OR set both 1.2.27 and 1.2.30 which solves both issues but is weird to look at from fixVersion field pov.

> Invalidate cache entries when getChildNodes() is aborted
> --------------------------------------------------------
>
>                 Key: OAK-6351
>                 URL: https://issues.apache.org/jira/browse/OAK-6351
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk
>            Reporter: Marcel Reutegger
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.7.2, 1.0.39, 1.4.17, 1.6.3, 1.8.0
>
>         Attachments: OAK-6351.patch
>
>
> With OAK-4623 {{DocumentNodeStore.getChildNodes()}} logs the document of the missing child node read directly from the document store. This effectively also ensures the document cache now contains an up-to-date version of the document.
> In addition the relevant cache entries in the node state and children caches should also be invalidated. As reported in OAK-6294, the system may still be stuck in this aborting state even if the document is now up-to-date.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)