clbarnes commented on issue #4611: URL: https://github.com/apache/arrow-rs/issues/4611#issuecomment-1842802493
> This would still be a breaking API change, something I am rather hesitant about. It would also not be object safe, which is likely more problematic. Understood. If we added `get_http_range` and `get_http_ranges` and then provided a default impl of `get_range` and `get_ranges` which used those under the hood (and marked them as deprecated), then 3rd party implementations would need to update but only in an additive way, new implementations wouldn't need to implement the limited methods, and people could continue to use their existing code. In this case it would definitely be nice to use a name more terse than `http_range`, though! The difficult bit would be getting 3rd party implementations to implement `get` in a way which respects the new `GetOptions::http_range` field. > Did you see, it would appear at least one of the major cloud providers do not support this Yes, tried to address that in my comment above. Sometimes people need the suffix, and on azure, the best those people can do is HEAD and GET range, but logging it so that users can change their access pattern if necessary is probably the right thing to do. -- 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]
