No. R2 is strongly consistent. If an operation succeeds then the thing happened. It’s on our backlog
No. R2 is strongly consistent. If an operation succeeds then the thing happened. It’s on our backlog to document the consistency guarantees specifically but GCS and S3 are very similar. Careful with 500 internal errors though. Just because an operation fails that way, it doesn’t mean nothing changed (eg maybe modification did happen or maybe it didn’t). I believe that’s only the case for 500 and random connection disconnects. All other errors typically have better defined semantics but I haven’t thought through if there’s some corner error case I didn’t think of where that isn’t the case.
