[jira] [Updated] (OAK-2242) provide a way to update the "created" timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-2242: -- Fix Version/s: (was: 1.3.9) 1.4 > 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.4 > > > 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)
[jira] [Updated] (OAK-2242) provide a way to update the "created" timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marcel Reutegger updated OAK-2242: -- Fix Version/s: (was: 1.3.7) 1.3.8 > 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.8 > > > 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)
[jira] [Updated] (OAK-2242) provide a way to update the "created" timestamp of a NodeDocument
[ 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.6) 1.3.7 > 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.7 > > > 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)
[jira] [Updated] (OAK-2242) provide a way to update the "created" timestamp of a NodeDocument
[ 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)
[jira] [Updated] (OAK-2242) provide a way to update the created timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2242: --- Labels: performance (was: ) 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.4 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)
[jira] [Updated] (OAK-2242) provide a way to update the created timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Marth updated OAK-2242: --- Fix Version/s: (was: 1.4) 1.3.7 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.7 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)
[jira] [Updated] (OAK-2242) provide a way to update the created timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Reschke updated OAK-2242: Fix Version/s: (was: 1.2) 1.4 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.4 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)
[jira] [Updated] (OAK-2242) provide a way to update the created timestamp of a NodeDocument
[ https://issues.apache.org/jira/browse/OAK-2242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Davide Giannella updated OAK-2242: -- Fix Version/s: (was: 1.1.2) 1.2 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)
