Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
Description
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.