crepererum commented on issue #5882: URL: https://github.com/apache/arrow-rs/issues/5882#issuecomment-2700954147
@Tangeroooo I think we're open for contributions to fix that. The essence is described in https://github.com/apache/arrow-rs/pull/6519#issuecomment-2621505087 or in my words: The `object_store` interface returns a stream of data. If that stream fails midway (e.g. because there's a timeout or a network glitch), retrying would need to make a new request with a new range starting after the last received byte and ideally also an ETAG/version check to ensure that the object that is returned by the retry is the the one that was already "in flight". This retry mechanic is obviously chaining/nested, i.e. if the retry fails mid-stream, you wanna have yet another retry that picks up the where the previous one ended. So long store short: People agree that this would be a good feature to have, but it requires a proper implementation. -- 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 For queries about this service, please contact Infrastructure at: us...@infra.apache.org
