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-2242) provide a way to update the "created" timestamp of a NodeDocument
Date Mon, 03 Nov 2014 15:49:36 GMT

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

Julian Reschke commented on OAK-2242:
-------------------------------------

In the meantime I changed RDB to check getLastCheckTime when accessing the cache and to set
it when a cache entry has been revalidated. [~mreutegg]] Is this something we should do in
Mongo as well?

> provide a way to update the "created" timestamp of a NodeDocument
> -----------------------------------------------------------------
>
>                 Key: OAK-2242
>                 URL: https://issues.apache.org/jira/browse/OAK-2242
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: mongomk
>    Affects Versions: 1.1.1
>            Reporter: Julian Reschke
>            Assignee: Julian Reschke
>             Fix For: 1.2
>
>
> Both the MongoDocumentStore and the RDBDocumentStore maintain a "_modCount" property,
which uniquely identifies a version of a document in the persistence.
> Sometimes, we read data from the persistence although we already might have the document
cached. This happens:
> a) when the cached document is older than what the caller asked for
> b) when running a query (for instance when looking up children of a node)
> In both cases, we currently replace the cache entry with a newly built NodeDocument.
> It would make sense to re-use the existing document instead. (This would probably require
modifying the "created" timestamp, but would avoid the trouble of having to update the cache
at all) 



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

Mime
View raw message