You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@opendal.apache.org by "wcy-fdu (via GitHub)" <gi...@apache.org> on 2025/08/04 02:59:57 UTC
After v0.51, how to specify list metakey?
GitHub user wcy-fdu created a discussion: After v0.51, how to specify list metakey?
>Users no longer need to pass the metakey into the list. Instead, services will make their best effort to return as much metadata as possible. Users can check items like Capability::list_has_etag before making a call.
The document mentions that v0.51 removed the list metakey and instead returned as many metakeys as possible. But I'm afraid there are still cases where metakey needs to be specified. For example, when we used fs backend before, we needed to specify metakey as Metakey::ContentLength | Metakey::LastModified, but now it seems that it will not be returned?
Now, can backends such as FS obtain this information when listing?
GitHub link: https://github.com/apache/opendal/discussions/6481
----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org
Re: After v0.51, how to specify list metakey?
Posted by "wcy-fdu (via GitHub)" <gi...@apache.org>.
GitHub user wcy-fdu added a comment to the discussion: After v0.51, how to specify list metakey?
Resolved:
I realized that we could get whether the field exist in list metadata via `native_capability.list_has_content_length` and get it by `stat`.
GitHub link: https://github.com/apache/opendal/discussions/6481#discussioncomment-13984660
----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org
Re: After v0.51, how to specify list metakey?
Posted by "wcy-fdu (via GitHub)" <gi...@apache.org>.
GitHub user wcy-fdu added a comment to the discussion: After v0.51, how to specify list metakey?
cc @Xuanwo PTAL❤️
GitHub link: https://github.com/apache/opendal/discussions/6481#discussioncomment-13981913
----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org
Re: After v0.51, how to specify list metakey?
Posted by "Xuanwo (via GitHub)" <gi...@apache.org>.
GitHub user Xuanwo added a comment to the discussion: After v0.51, how to specify list metakey?
Thank you for the research!
GitHub link: https://github.com/apache/opendal/discussions/6481#discussioncomment-13985220
----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org
Re: After v0.51, how to specify list metakey?
Posted by "wcy-fdu (via GitHub)" <gi...@apache.org>.
GitHub user wcy-fdu closed a discussion: After v0.51, how to specify list metakey?
>Users no longer need to pass the metakey into the list. Instead, services will make their best effort to return as much metadata as possible. Users can check items like Capability::list_has_etag before making a call.
The document mentions that v0.51 removed the list metakey and instead returned as many metakeys as possible. But I'm afraid there are still cases where metakey needs to be specified. For example, when we used fs backend before, we needed to specify metakey as Metakey::ContentLength | Metakey::LastModified, but now it seems that it will not be returned?
Now, can backends such as FS obtain this information when listing?
GitHub link: https://github.com/apache/opendal/discussions/6481
----
This is an automatically sent email for dev@opendal.apache.org.
To unsubscribe, please send an email to: dev-unsubscribe@opendal.apache.org