Add missing fields as per S3 specification#1618
Conversation
balamurugana
force-pushed
the
Add-missing-fields-as-per-S3-specification
branch
from
0fc2947 to
2dc3195
Compare
balamurugana
force-pushed
the
Add-missing-fields-as-per-S3-specification
branch
2 times, most recently
from
0ee6b79 to
cdceb4b
Compare
balamurugana
force-pushed
the
Add-missing-fields-as-per-S3-specification
branch
3 times, most recently
from
bd5d6ef to
e58019e
Compare
* listBuckets(ListBucketsArgs) breaks backward compatibility due to unlimited bucket listing Signed-off-by: Bala.FA <[email protected]>
balamurugana
force-pushed
the
Add-missing-fields-as-per-S3-specification
branch
from
e58019e to
1005fa8
Compare
| } | ||
|
|
||
| @Root(name = "EventBridgeConfiguration") | ||
| public static class EventBridgeConfiguration {} |
There was a problem hiding this comment.
do we plan to implement this in future with details?
There was a problem hiding this comment.
I do not see any fields in S3 specification. It is empty ATM
|
Hi @balamurugana , apologies if this is the wrong avenue for such a question; I didn't find contact instructions in the project readme. I'm wondering, do you know when the changes from this PR will make it to the next release? I'm currently using the latest release (8.5.17), where CompleteMultipartUploadOutput is still missing the "ChecksumCRC64NVME" field and (if I'm reading correctly) needs to be renamed to CompleteMultipartUploadResult. I believe this is resulting in the warning below in our logs every time there's an upload to S3. I think this is not really causing problems, because I can see from the Minio client code that the warning is logged despite successful upload, but I'd like to keep track of when we can upgrade and stop seeing this in our logs. Thanks for your time! |
5 participants
unlimited bucket listing