Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Docs] Document conventions for sending and receiving Arrow data over HTTP APIs #40465

Open
19 of 33 tasks
ianmcook opened this issue Mar 11, 2024 · 4 comments
Open
19 of 33 tasks

Comments

@ianmcook
Copy link
Member

ianmcook commented Mar 11, 2024

Describe the enhancement requested

The Arrow developer community intends to publish a set of conventions in the Arrow docs for how to send and receive Arrow-format data over HTTP APIs. There is a related discussion on the Arrow developer mailing list at https://lists.apache.org/thread/886cnx6ytjst3smmytz4r4ddcbv95191.

Tasks

This issue is an umbrella for tasks that are a part of this effort.


Simple HTTP GET client and server examples

📁 arrow-experiments/tree/main/http/get_simple


HTTP GET client and server examples demonstrating range requests

📁 arrow-experiments/tree/main/http/get_range


Indirect response HTTP GET client and server examples

📁 arrow-experiments/tree/main/http/get_indirect


Multipart/mixed response HTTP GET client and server examples

📁 arrow-experiments/tree/main/http/get_multipart


HTTP GET examples to test different compression options

📁 arrow-experiments/tree/main/http/get_compressed


Simple HTTP PUT / POST client and server examples

📁 arrow-experiments/tree/main/http/post_simple


Multipart/form-data request HTTP PUT / POST client and server examples

📁 arrow-experiments/tree/main/http/post_multipart


General issues and questions


Component(s)

Documentation

@felipecrv
Copy link
Contributor

Is this the main issue where I can track your HTTP+Arrow initiative @ianmcook?

@ianmcook
Copy link
Member Author

Is this the main issue where I can track your HTTP+Arrow initiative @ianmcook?

Yes

@CurtHagenlocher
Copy link
Contributor

Any thoughts on the "best" canonical way to return multiple record batches? Would that also be multipart/mixed or would it be better to avoid the delimiter problem and e.g. use an alternate Content-Type indicating that the response contains multiple streams?

@ianmcook
Copy link
Member Author

ianmcook commented Apr 3, 2024

Any thoughts on the "best" canonical way to return multiple record batches? Would that also be multipart/mixed or would it be better to avoid the delimiter problem and e.g. use an alternate Content-Type indicating that the response contains multiple streams?

@CurtHagenlocher Let's discuss this at #40596 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants