You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would be helpful in Azurite, for example, to draft solutions for cleanup mechanisms that go beyond the abilities of lifecycle management policies, or for synchronization mechanisms based on data usage.
There appears to be a sole mention for lastaccesstime in the code
I can't make any promises, but I might take a look. Would you prefer having this feature always-on, or controllable somehow? In Azure, last access time tracking (and versionid) would be defined (and changeable) for each storage account.
Does Azurite already have a similar concept to build on?
Thanks for the detail question!
Yes, Azurite is a storage data plane rest API emulator, not support control plane rest API which can enable last access time tracking (and versionid)...
There are 2 ways to add the support:
Add a new parameter to enable LAT
Add a configure file for all storage control plane setting.
Option 2 might will be better, as other new feature with control plane setting can also utilize it.
Dear Azurite developers,
Would it be feasible to add support for last access time tracking for blobs in Azurite?
On Azure, this can be enabled as following:
https://learn.microsoft.com/en-us/azure/storage/blobs/lifecycle-management-policy-configure?tabs=azure-portal#optionally-enable-access-time-tracking
and results in operations such as List Blobs to return the attribute
properties:lastaccesstime
for every blob.This would be helpful in Azurite, for example, to draft solutions for cleanup mechanisms that go beyond the abilities of lifecycle management policies, or for synchronization mechanisms based on data usage.
There appears to be a sole mention for lastaccesstime in the code
Azurite/src/blob/generated/artifacts/mappers.ts
Line 439 in c3f9344
Thank You
Maik
The text was updated successfully, but these errors were encountered: