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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/05/04 10:53:12 UTC

[jira] [Updated] (OAK-4320) Use the cache tracker in the RDB Document Store

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

Tomek Rękawek updated OAK-4320:
-------------------------------
    Attachment: OAK-4320-2.patch

> 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-2.patch, 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
(v6.3.4#6332)