[
https://issues.apache.org/jira/browse/JCR-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashank Gupta updated JCR-3547:
--------------------------------
Description:
In mark phase, GC updates store.updateModifiedDateOnAccess with current time,
so that datastore updates record’s lastModified timestamp upon subsequent
read/scan.
But GC doesn't reset it to 0. So even after GC completes, datastore will
continue updating lastModified timestamp on read invocations and it will have
performance impact.
was:
In mark phase, GC updates store.updateModifiedDateOnAccess with current time,
so that datastore updates record’s lastModified timestamp upon subsequent
read/scan.
But GC doesn't resetting it to original value. So even after GC completes,
datastore will continue updating lastModified timestamp on read. It will have
performance impact on read invocations.
> Datastore GC doesn't reset updateModifiedDateOnAccess on datastore
> ------------------------------------------------------------------
>
> Key: JCR-3547
> URL: https://issues.apache.org/jira/browse/JCR-3547
> Project: Jackrabbit Content Repository
> Issue Type: Bug
> Components: jackrabbit-core
> Affects Versions: 2.4, 2.5
> Reporter: Shashank Gupta
>
> In mark phase, GC updates store.updateModifiedDateOnAccess with current time,
> so that datastore updates record’s lastModified timestamp upon subsequent
> read/scan.
> But GC doesn't reset it to 0. So even after GC completes, datastore will
> continue updating lastModified timestamp on read invocations and it will have
> performance impact.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
