Stupid. A lot of people using the actual Amazon S3 for production, are also using S3 API with minio for local testing.
minio at least was updated to always emit the header, so it's simply an upgrade away.
AWS S3 SDK breaks its compatible services
11–20 of 91 posts
Re: AWS S3 SDK breaks its compatible services
#12Okay, but I'd never expect an AWS SDK to remain backwards compatible with third-party services and would be leery about using an AWS SDK with anything but AWS. It's on the third parties to keep their S3-compatible API, well, compatible. On the client side, you just have to pin to an older version of the AWS SDK till whatever compatible service you're using updates, right? Also, this is the first I've heard of OpenDAL…
Hard agree. If AWS were offering “S3 compatibility certification” or similar I could see framing this as an AWS/S3 problem. This seems like the definition of “S3 compatible” changed, and now everyone claiming it needs to catch up again.
Re: AWS S3 SDK breaks its compatible services
#13Does AWS S3 SDK have a list of "compatible services" ?
Re: AWS S3 SDK breaks its compatible services
#14Okay, but I'd never expect an AWS SDK to remain backwards compatible with third-party services and would be leery about using an AWS SDK with anything but AWS. It's on the third parties to keep their S3-compatible API, well, compatible. On the client side, you just have to pin to an older version of the AWS SDK till whatever compatible service you're using updates, right? Also, this is the first I've heard of OpenDAL…
It should be fairly easy to upgrade compatible APIs server side from reading the AWS docs. All that needs doing is to accept and ignore the new checksum header. I also expect that taking advantage of the checksum would be reasonable, a CRC32 isn't that hard.
https://aws.amazon.com/blogs/aws/introducing-default-data-in...
Re: AWS S3 SDK breaks its compatible services
#15Y'all put blind trust in a proprietary API SDK and all the eggs in the same basket? Just like that??
Re: AWS S3 SDK breaks its compatible services
#16[flagged]
Re: AWS S3 SDK breaks its compatible services
#17Stupid. A lot of people using the actual Amazon S3 for production, are also using S3 API with minio for local testing. minio at least was updated to always emit the header, so it's simply an upgrade away.
Production is less dependant on local testing, and minio can presumably move fast.
It's not on Amazon to support every edge case for every customer.
Re: AWS S3 SDK breaks its compatible services
#18I've always been very uncomfortable with the S3 API becoming a defacto protocol, and this shows why.
Re: AWS S3 SDK breaks its compatible services
#19[flagged]
SCP isn't region replicated.
Re: AWS S3 SDK breaks its compatible services
#20The expectation that S3 should not improve functionality for paying customers because other people use the SDK for something completely unrelated is asinine.