cls/rgw: fix rgw list-object-versions key-marker behavior to match s3#60280
cls/rgw: fix rgw list-object-versions key-marker behavior to match s3#60280
Conversation
The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit updates RGW's behavior to make the key-marker parameter exclusive, ensuring consistent behavior between RGW and S3. Fixes: https://tracker.ceph.com/issues/68055 Signed-off-by: Samaksh Dhingra <[email protected]>
|
new test cases from ceph/s3-tests#594 passed:
|
|
@samakshd, thanks for noticing that! Have you looked into why this extra check is even necessary since the functions are all coded as exclusive?
That in turn calls And ultimately this is called, and the parameter is named If there's a logic error in that chain, I would prefer a solution that fixed it rather than checking each entry returned. So I'm wondering if you traced that through and what ideas you might have towards that. Thanks! |
ivancich
left a comment
There was a problem hiding this comment.
I would prefer a fix that resolved an apparent logic error rather than checking each value.
|
Also, I want to apologize for the very late review, @samakshd! |
|
jenkins test make check |
|
Can one of the admins verify this patch? |
|
This pull request has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs for another 30 days. |
|
This pull request has been automatically closed because there has been no activity for 90 days. Please feel free to reopen this pull request (or open a new one) if the proposed change is still appropriate. Thank you for your contribution! |
The key-marker parameter in the list-object-versions operation is inclusive in RGW, while it's exclusive in S3. This commit updates RGW's behavior to make the key-marker parameter exclusive, ensuring consistent behavior between RGW and S3.
Fixes: https://tracker.ceph.com/issues/68055
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 retest this pleasejenkins test classic perfjenkins test crimson perfjenkins test signedjenkins test make checkjenkins test make check arm64jenkins test submodulesjenkins test dashboardjenkins test dashboard cephadmjenkins test apijenkins test docsjenkins render docsjenkins test ceph-volume alljenkins test ceph-volume toxjenkins test windowsjenkins test rook e2e