[
https://issues.apache.org/jira/browse/OAK-3494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947017#comment-14947017
]
Vikas Saurabh edited comment on OAK-3494 at 10/7/15 3:29 PM:
-------------------------------------------------------------
Attached [patch|^OAK-3494.patch] (which includes the test case patch from
above).
[~mreutegg], [~egli] can you guys please review? I'm completely unsure if I've
used Jsop parsing correctly.
was (Author: catholicon):
Attached [patch|OAK-3494.patch] (which includes the test case patch from above).
[~mreutegg], [~egli] can you guys please review? I'm completely unsure if I've
used Jsop parsing correctly.
> MemoryDiffCache should also check parent paths before falling to Loader (or
> returning null)
> -------------------------------------------------------------------------------------------
>
> Key: OAK-3494
> URL: https://issues.apache.org/jira/browse/OAK-3494
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: core
> Reporter: Vikas Saurabh
> Labels: performance
> Attachments: OAK-3494-TestCase.patch, OAK-3494.patch
>
>
> Each entry in {{MemoryDiffCache}} is keyed with {{(path, fromRev, toRev)}}
> for the list of modified children at {{path}}. A diff calcualted by
> {{DocumentNodeStore.diffImpl}} at '/' (passively via loader) or
> {{JournalEntry.applyTo}} (actively) fill each path for which there are
> modified children (including the hierarchy)
> But, if an observer calls {{compareWithBaseState}} on a unmodified sub-tree,
> the observer will still go down to {{diffImpl}} although cached parent entry
> can be used to answer the query.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
