calavera opened a new issue, #464: URL: https://github.com/apache/arrow-rs-object-store/issues/464
**Is your feature request related to a problem or challenge? Please describe what you are trying to do.** <!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] (This section helps Arrow developers understand the context and *why* for this feature, in addition to the *what*) --> Put operations in object store are usually idempotent. However, that guarantee does not exist since this crate calls APIs that it does not control. Some clients might want to take the risk of ensuring all `put` operations are idempotent, and retried when unexpected errors happen, like SlateDB. I'm bringing the discussion of allow flagging operations as idempotent here, since I believe it'd be better solved in this repository. **Describe the solution you'd like** <!-- A clear and concise description of what you want to happen. --> I'd like to add a flag to `PutOptions` that people can use to make `PUT` operations idempotent. **Describe alternatives you've considered** <!-- A clear and concise description of any alternative solutions or features you've considered. --> The only alternative is to force consumers of this library to implement their own retry logic. Even if this is doable, it adds repetition and additional complexity to people that want to integrate this crate in their applications. The SDKs and HTTP libraries that call the cloud providers APIs already implement retry logic that we can leverage. **Additional context** <!-- Add any other context or screenshots about the feature request here. --> See https://github.com/slatedb/slatedb/issues/766 for context. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: github-unsubscr...@arrow.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
