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
I'm not sure this is something that needs to be addressed in adlfs, but I think it's worth noting that etags returned by fs.info() and fs.ls(detail=True) have different formats. When using fs.info() the etag will be quoted (wrapped in " quotes) but when using fs.ls() the etag will not be quoted. This means that the caller has to correct the quote format before being able to compare etags to see whether a file has been modified.
I did some investigation and it looks like this is due to differences in what the azure API returns for different calls. When using BlobClient.get_blob_properties() the returned etag property is wrapped in " quotes. However, when using BlobContainer.walk_blobs() the etag property for iterated blob properties is not wrapped in quotes.
The text was updated successfully, but these errors were encountered:
I'm not sure this is something that needs to be addressed in adlfs, but I think it's worth noting that etags returned by
fs.info()
andfs.ls(detail=True)
have different formats. When usingfs.info()
the etag will be quoted (wrapped in"
quotes) but when usingfs.ls()
the etag will not be quoted. This means that the caller has to correct the quote format before being able to compare etags to see whether a file has been modified.With adlfs 2024.2.0:
I did some investigation and it looks like this is due to differences in what the azure API returns for different calls. When using
BlobClient.get_blob_properties()
the returned etag property is wrapped in"
quotes. However, when usingBlobContainer.walk_blobs()
the etag property for iterated blob properties is not wrapped in quotes.The text was updated successfully, but these errors were encountered: