Hey All, I would like to propose extending the semantics for Flight RPC Location URI messages as documented in a PR [1] currently filed on the main Arrow Repo.
Previous discussions can be found at [2] and [3]. After discussion on the PR, the entirety of the change mostly boils down to allowing the URI to be an HTTP or HTTPS URL that a client would make a GET request against to retrieve the data as a file (Arrow IPC Stream, Parquet, or otherwise) identified by the content-type header. See the changes in the PR [1] for the specifics and other semantic information such as handling Auth, Accept headers, Cloud Storage, and so on. The vote will be open for at least 72 hours. [ ] +1 Accept this proposal [ ] +0 [ ] -1 Do not extend flight location URIs because... Thanks everyone! --Matt [1]: https://github.com/apache/arrow/pull/46194 [2]: https://lists.apache.org/thread/y4sb8fvftbv3x72pzqofcb0m43zd1j9j [3]: https://lists.apache.org/thread/qmgfzy8ofrdk6bv1rknnnj2ls5cqytzq
