Hi all,

I've put together two more proposals for Flight, motivated by projects
we've been working on. I'd appreciate any comments on the
design/reasoning; I'm already working on the implementation, alongside
some other improvements to Flight.

The first is to modify the DoPut call to follow the same request
pattern as DoGet. This is a format change and would require a vote.

https://docs.google.com/document/d/1hrwxNwPU1aOD_1ciRUOaGeUCyXYOmu6IxxCfY6Stj6w/edit?usp=sharing

---

The second is to introduce a middleware API for Flight, to make
integration with logging and tracing frameworks (e.g. OpenTracing)
easier:

https://docs.google.com/document/d/1Nm1ASp6w5PZQX42KkOTLK5LvrOv5q2cCbkaiVjqKjLU/edit?usp=sharing

As part of this, I'm working on APIs to send richer error
codes/messages between Flight clients/servers, now that @Micah has
enabled custom error codes in Arrow-C++. These are API changes and
should not require a vote, I believe.

---

Anyone should have comment access to these documents, but let me know if not.

Thanks!

Best,
David

Reply via email to