rgw: add wildcard "*" support for conditional read#64428
Conversation
|
@cbodley Hello, could you please check this PR? Also I would really appreciate if you could share if some other works(ex. document update or creating issue ticket) need to be done. |
248a961 to
baaed21
Compare
baaed21 to
9212290
Compare
|
To test: |
|
@AliMasarweh Thank you for the review! Do I need to do something before merging this commit? |
you are welcome :) |
|
@AliMasarweh Thank you for the reply. However, I'm a beginner contributor to Ceph and I'm trying to figure out how to run Teuthology tests. I've read that I can run them in the Sepia lab, is that the right way to do it? If so, could you please provide me with access? Thanks! I filed a ticket. |
I am not responsible for providing access to people, but I will ask someone who can provide you access |
thanks @sungjoon-koh. it would be great if you could turn this into test cases in s3-tests so we can validate this pr |
9212290 to
71d21b1
Compare
|
s3 tests for this pr: ceph/s3-tests#681 |
|
Many test cases seem to be failing, but most of them appear unrelated to my modifications. |
Lots of failures on test test_get_account_summary_root |
71d21b1 to
e96f968
Compare
Thank you for checking. I will rebase and check it again. |
e96f968 to
6e28ac3
Compare
|
jenkins test make check |
|
jenkins test make check arm64 |
|
jenkins test windows |
- Enhanced If-Match and If-None-Match headers to support the wildcard "*". - Updated conditional read behavior: - If-Match: * now returns 200 instead of 412 when any object exists. - If-None-Match: * now returns 304 instead of 200 when any object exists. - If-Match: * + If-None-Match: * now returns 304 instead of 412. - Aligns with AWS S3 expected functionality for improved efficiency. Signed-off-by: sungjoon_koh <sungjoon_koh@linecorp.com>
6e28ac3 to
beba28f
Compare
|
jenkins test make check |
|
jenkins test make check arm64 |
|
Ali Masarweh suggested I reach out to you for confirmation regarding some RGW teuthology test results. After discussing with Ali, he mentioned that:
Could you please help confirm whether these results look acceptable for my PR? Thank you. |
|
pr testing completed : https://tracker.ceph.com/issues/73008 and got approved by @ivancich |
|
@anrao19 Thank you for the test! Who do I need to ask for PR approval? |
I have asked for review, will wait for some time post approval we can merge |
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
xbetween the brackets:[x]. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins test classic perfJenkins Job | Jenkins Job Definitionjenkins test crimson perfJenkins Job | Jenkins Job Definitionjenkins test signedJenkins Job | Jenkins Job Definitionjenkins test make checkJenkins Job | Jenkins Job Definitionjenkins test make check arm64Jenkins Job | Jenkins Job Definitionjenkins test submodulesJenkins Job | Jenkins Job Definitionjenkins test dashboardJenkins Job | Jenkins Job Definitionjenkins test dashboard cephadmJenkins Job | Jenkins Job Definitionjenkins test apiJenkins Job | Jenkins Job Definitionjenkins test docsReadTheDocs | Github Workflow Definitionjenkins test ceph-volume allJenkins Jobs | Jenkins Jobs Definitionjenkins test windowsJenkins Job | Jenkins Job Definitionjenkins test rook e2eJenkins Job | Jenkins Job Definition