clbarnes commented on issue #4611: URL: https://github.com/apache/arrow-rs/issues/4611#issuecomment-1842778033
I think I'm closing in on an implementation here. Allowing suffixes could mean that some bytes are fetched twice but I don't think that's too much of a problem, as it's on the user to have knowledge of the resource they're looking into. I've been using `HttpRange` as the type name (and in all the functions which use it) - would be nice to have something more terse but it's the best description I think, even for stores which aren't HTTP-backed. I think that replacing references to `Range<usize>` in the API with `T: Into<HttpRange> + Copy` should make for a seamless upgrade path, but the `range` field on the `GetOptions` struct would need to be deprecated and a different field of type `HttpRange` (called `http_range`?), probably raising an error if both are defined. What we do with suffixes on azure is another question - probably just a `log_once::warn_once!()` when a suffix is requested, and then a HEAD request to find the length and regular range request. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
