[ https://issues.apache.org/jira/browse/OAK-9063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nitin Gupta closed OAK-9063. ---------------------------- > Use a custom metadata property to manage lastModified in AzureDataStore > ----------------------------------------------------------------------- > > Key: OAK-9063 > URL: https://issues.apache.org/jira/browse/OAK-9063 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: blob-cloud-azure > Reporter: Amit Jain > Assignee: Amit Jain > Priority: Major > Fix For: 1.30.0 > > Attachments: OAK-9063.patch > > > Currently, the lastModified property managed by azure is used but then to > update the timestamp a copy operation is performed in the blob to itself. > Besides inefficient, this operation sometimes causes problems if the copy > operation is perfomed just after a blob wrrite in a parallel thread. > This issue changes the behaviour to manage the timestamp through a custom > metadata property. While retrieving a fallback to azure managed timestamp is > to bee used in case the metadata property is not available. > -- This message was sent by Atlassian Jira (v8.3.4#803005)