My team uses Flight this way as well. We just use DoGet, DoPut, or
DoExchange, depending on whether we're reading a stream of record batches,
writing a stream, or need some sort of bidirectional communication. We
also have full control over clients and servers, and simply use JSON in the
Flight m
Yes, there's really no problem if you just want to use Flight as a pipe for
Arrow data.
(There's also a proposal to inline data directly into FlightInfo, if you want
to keep the separate metadata.)
On Fri, Feb 3, 2023, at 17:44, Aldrin wrote:
> I am planning on doing something similar, but I do
I am planning on doing something similar, but I don't have a concrete
reference to point you to.
In my case, I am treating the metadata as something that is re-usable (e.g.
the FlightInfo is not something that expires after the first use).
This makes the most sense when the information in FlightIn
