Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mc find --metadata not working #4790

Closed
oernii opened this issue Dec 14, 2023 · 2 comments · Fixed by #4926
Closed

mc find --metadata not working #4790

oernii opened this issue Dec 14, 2023 · 2 comments · Fixed by #4926
Assignees

Comments

@oernii
Copy link

oernii commented Dec 14, 2023

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

@vadmeste
Copy link
Member

vadmeste commented Dec 15, 2023

@oernii what will work now is:

mcli find --metadata "X-Amz-Meta-Testname=33" alias/bucket/

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
Copy link
Member

@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 ?

yeah it makes sense @vadmeste

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants