pohlm01 opened a new issue, #508:
URL: https://github.com/apache/arrow-rs-object-store/issues/508

   We are currently migrating an application from Google Storage to a S3 
compatible object storage of another provider. Currently, we rely on the 
`google-cloud-storage` crate and are using the 
[`patch_object`](https://docs.rs/google-cloud-storage/0.24.0/google_cloud_storage/http/storage_client/struct.StorageClient.html#method.patch_object)
 method to update metadata on an existing object. It seems that `object_store` 
has 
[support](https://docs.rs/object_store/0.12.4/object_store/struct.PutOptions.html#structfield.tags)
 for object metadata as well, it's just called **tag** here. The difficulty I'm 
facing is that the `object_store` seems to only allow setting tags during 
object creation, but not as a patch later on, nor does it allow getting the 
current tags of an object. Especially, the later dramatically limits the user 
case.
   From my short research, it seems that all big three cloud solutions support 
such tags 
([s3](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-tagging.html),
 
[gcs](https://cloud.google.com/storage/docs/viewing-editing-metadata#command-line),
 
[azure](https://learn.microsoft.com/en-us/rest/api/storageservices/set-blob-tags?tabs=microsoft-entra-id#request-body)).
 
   <!--
   A clear and concise description of what the problem is. Ex. I'm always 
frustrated when [...] 
   (This section helps Arrow developers understand the context and *why* for 
this feature, in addition to  the *what*)
   -->
   
   **Describe the solution you'd like**
   <!--
   A clear and concise description of what you want to happen.
   -->
   Firstly, I would like to be able to retrieve existing tags from objects via 
the `get` and `head` methods. As an improvement, it would be nice to provide 
methods that allow patching an existing object to modify its tags.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to