[
https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-2242:
---------------------------
Fix Version/s: (was: 1.3.7)
1.3.6
> 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
> Labels: performance
> Fix For: 1.3.6
>
>
> 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)
