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/07/21 12:50:20 UTC

[jira] [Resolved] (OAK-4587) Don't ignore the cached NULLs in bulk createOrUpdate for Mongo

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

Tomek Rękawek resolved OAK-4587.
--------------------------------
    Resolution: Fixed

> Don't ignore the cached NULLs in bulk createOrUpdate for Mongo
> --------------------------------------------------------------
>
>                 Key: OAK-4587
>                 URL: https://issues.apache.org/jira/browse/OAK-4587
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>            Reporter: Tomek Rękawek
>            Assignee: Tomek Rękawek
>              Labels: performance
>             Fix For: 1.6, 1.4.6, 1.5.7
>
>
> The bulk createOrUpdate operation needs to have old versions of all updated documents. If some documents are not in the cache, they are requested from the Mongo. However, if the document key is cached with the NULL value (which means it doesn't exists), the createOrUpdate ignores such information and tries to load the document from Mongo anyway.
> We shouldn't ignore these NULLs but assume that keys cached with the NULL value indicate an non-existing document.
> If the document exists (because the cache became outdated), the sendBulkUpdate() method will detect it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)