clbarnes commented on issue #4611: URL: https://github.com/apache/arrow-rs/issues/4611#issuecomment-1842822073
> The difficult bit would be getting 3rd party implementations to implement get in a way which respects the new GetOptions::http_range field. Marking range as deprecated would at least give visibility to developers but it could easily be ignored. Actually, just noticed we control this too - it's just a case of updating `GetOptionsExt`. We'd need to decide what to do if someone sent *both* a `range` and an `http_range` in their `GetOptions`; choosing the `http_range` and logging a warning is probably best, if not panicking as it's purely a user error that they should be getting a clear deprecation warning about. -- 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]
