jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julian Reschke (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4320) Use the cache tracker in the RDB Document Store
Date Mon, 02 May 2016 10:11:12 GMT

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

Julian Reschke commented on OAK-4320:

I had another look at the change, and it removes an optimization that I think was useful;
not re-parsing a document from the DB when we already have it in the case (this was in {{runThroughCache()}}.
Was that change intentional (in that you think the optimization isn't worth the complexity?)?

> Use the cache tracker in the RDB Document Store
> -----------------------------------------------
>                 Key: OAK-4320
>                 URL: https://issues.apache.org/jira/browse/OAK-4320
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk, rdbmk
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>             Fix For: 1.6
>         Attachments: OAK-4320.patch
> OAK-4112 introduced {{CacheChangesTracker}} mechanism, inspired by the {{QueryContext}}
class, already present in the RDB DS.
> The tracker works on the {{NodeDocumentCache}} level, within the methods modifying the
cache values, using the same {{NodeDocumentLocks}}, which may prevent potential concurrency
problems, described in the comments to OAK-3566.
> We should synchronise both approaches, so the queries in Mongo and RDB uses the same
logic to update their caches.

This message was sent by Atlassian JIRA

View raw message