-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add additional_blob_attributes to upload_many_from_filenames #1162
Conversation
|
||
file_blob_pairs = [] | ||
|
||
for filename in filenames: | ||
path = os.path.join(source_directory, filename) | ||
blob_name = blob_name_prefix + filename | ||
blob = bucket.blob(blob_name, **blob_constructor_kwargs) | ||
for prop, value in additional_blob_attributes.items(): | ||
setattr(blob, prop, value) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason not to use blob._patch_property()
that is broadly used in the library? Blob property changes are propagated through blob._get_writable_metadata
and blob._get_upload_arguments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did consider that but decided there was no need to use a private method on the blob class when the typical public interface of attribute assignment would do the same thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm curious how the blob properties are actually picked up in blob._changes
. I thought we're relying on blob._changes
to get writable metadata for the upload arguments
python-storage/google/cloud/storage/blob.py
Lines 1708 to 1713 in c5a983d
object_metadata = {"name": self.name} | |
for key in self._changes: | |
if key in _WRITABLE_FIELDS: | |
object_metadata[key] = self._properties[key] | |
return object_metadata |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the _PropertyMixin, all the fields set as a _scalar_property have a custom setter that updates _changes. This solution using setattr will also activate that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah I see, that makes sense, thanks! One last nit on the naming, maybe consider additional_blob_properties
for consistency? Property is used in the official docs and in the lib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha, that was actually the name in my first revision.
I changed it to "attributes" because it's not only _scalar_property but any attribute that we can set with setattr. Also, since we're using setattr the nomenclature matches.
I'm going to add a system test to this before merging, working on it now. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Fixes #996 🦕