You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All user custom metadata starts with X-Amz-Meta- in S3. This is not user friendly for now; we can use what is the best way to address this.
@harshavardhana does it make sense to differentiate between "standard" headers and unrecognized metatdata key and add X-Amz-Meta- in that case before comparing it with objects metadata found in the server ?
@harshavardhana does it make sense to differentiate between "standard" headers and unrecognized metatdata key and add X-Amz-Meta- in that case before comparing it with objects metadata found in the server ?
Expected behavior
"mcli find --metadata" prints existing documents matching existing metadata
Actual behavior
"mcli find --metadata" returns nothing
Steps to reproduce the behavior
mcli cp /proc/cpuinfo --attr testname=33 alias/bucket/testfile
mcli stat alias/bucket/testfile --versions
mcli find --metadata testname=33 alias/bucket/
mc --version
mcli version RELEASE.2023-12-14T00-37-41Z (commit-id=8da737f8fd63de58dc475bf88eb9e285d206e3ae)
Runtime: go1.21.5 linux/amd64
System information
RHEL8.9
The text was updated successfully, but these errors were encountered: