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
Not sure if it is by design but I have noticed that in order to read the metadata of a blob, the library actually downloads it, before parsing and rendering the metadata dict.
If this is the case, this is highly inefficient e.g. one needs to download a 2GB file to read the content_type or any custom metadata.
If confirmed, this is a showstopper for us.
Also, list_blobs only returns name so can't use it to read the metadata - which would be more efficient.
The text was updated successfully, but these errors were encountered:
Not sure if it is by design but I have noticed that in order to read the metadata of a blob, the library actually downloads it, before parsing and rendering the metadata dict.
If this is the case, this is highly inefficient e.g. one needs to download a 2GB file to read the content_type or any custom metadata.
If confirmed, this is a showstopper for us.
Also,
list_blobs
only returnsname
so can't use it to read the metadata - which would be more efficient.The text was updated successfully, but these errors were encountered: