thinkharderdev commented on issue #5334: URL: https://github.com/apache/arrow-rs/issues/5334#issuecomment-1912825375
Sounds good in general ``` We can't add Attributes to ObjectMeta as the listing APIs do not return this information. ``` Would we add another method like `get_object_attributes(&self,object_meta: &ObjectMeta) -> Result<Attributes>`? Also, certain attributes may be returned by `head` (thinking specifically of storage class in AWS, which is something we've had to deal with recently), would those be added to the `ObjectMeta`. ``` Whilst the Attribute mechanism doesn't eliminate this issue, as not all implementations will support all Attribute ``` Is the idea that `Attributes` will encode a superset of metadata across all first-party store implementations? It's not the most elegent thing in the world but an explicit API for `supports_attribute(&self, attribute: Attribute) -> bool` could be useful for writing store-implementation-independent code since you can write branching logic based on what attributes are supported on the application side. -- 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]
