tokoko commented on code in PR #46194: URL: https://github.com/apache/arrow/pull/46194#discussion_r2053969336
########## docs/source/format/Flight.rst: ########## @@ -369,6 +369,61 @@ string, so the obvious candidates are not compatible. The chosen representation can be parsed by both implementations, as well as Go's ``net/url`` and Python's ``urllib.parse``. +Extended Location URIs +---------------------- + +In addition to alternative transports, a server may also return +URIs that reference an external service or object storage location. +This can be useful in cases where intermediate data is cached as +Apache Parquet files on S3 or is accessible via an HTTP service. In +these scenarios, it is more efficient to be able to provide a URI +where the client may simply download the data directly, rather than +requiring a Flight service to read it back into memory and serve it +from a ``DoGet`` request. Servers should use the following URI +schemes for this situation: + ++--------------------+------------------------+ +| Location | URI Scheme | ++====================+========================+ +| Object storage (1) | s3:, gcs:, abfs:, etc. | Review Comment: Since the change is essentially about delegating data access to a different protocol, feels like it should be fine to delegate the particulars of URI syntax and such to wherever that protocol is defined as well. Unless you have some particular parameter in mind (of s3 for example) that doesn't make sense in the context of flight. Realistically clients wouldn't try to reimplement each protocol (?), rather they will integrate with existing tools that probably aim to cover the full spec regardless. I think a major upside of having an exhaustive list would be to at least signal to clients what the goalpost should be. There should be some way to state that it's lot more likely to encounter s3/parquet duo in the response rather than ftp/orc for example. Disallowing combinations like ftp/orc altogether would be a simple way to achieve this. -- 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
