Arvados

19088-s3-properties-tags @ dd8f1b0527995bc5ad47710d3a483fa18b827bc6 -- developer-run-tests: #3202

Tom Clegg wrote in #note-12:

19088-s3-properties-tags @ dd8f1b0527995bc5ad47710d3a483fa18b827bc6 -- developer-run-tests: #3202

Is there any particular reason you didn't implement GetBucketTagging and GetObjectTagging?

https://docs.aws.amazon.com/AmazonS3/latest/API/API_GetObjectTagging.html

The difference between these and HeadObject seems to be that they returns an XML document rather than embedding it in the headers. Which sounds annoying, but someone might want it, I don't know.

I did some looking, I didn't realize that there's no listing API that can return objects with tags to even be able to do client side filtering efficiently. Clients will have to get the tags of every object separately, which is going to be pretty terrible. Hopefully the keep-web response in that case (once cached) be will be very fast and efficient.

Oops, not really. I just happened to know about the metadata headers and assumed that's what was being asked.

Being readonly, I think it should be just as easy to export the same info in other ways too, if it turns out people really want to use the tagging API.

Tom Clegg wrote in #note-14:

Oops, not really. I just happened to know about the metadata headers and assumed that's what was being asked.

Being readonly, I think it should be just as easy to export the same info in other ways too, if it turns out people really want to use the tagging API.

Per our conversation, we agreed to merge now and support APIs for tagging later if someone asks.

It just occurred to me that we should be totally clear about what is supported and what isn't in the documentation, so someone doesn't try to use e.g. GetObjectTagging and then wonder why it didn't work.

(I'm writing this after you merged the branch so a quick follow-on documentation tweak commit would be appreciated it)