Hi Wes A client usually needs to contact a control plane to find out an "execution plan" before it can write to data plane end points. The control plane might authorize the put, decide where to write, and encode all that into a ticket as part of the flightinfo. the ticket could be used not just as a "query plan"
Thanks Ming On Mon, Jun 3, 2019 at 11:55 AM Wes McKinney <wesmck...@gmail.com> wrote: > hi Ming, > > See comment on the FlightDescriptor member of FlightData: > > https://github.com/apache/arrow/blob/master/format/Flight.proto#L281 > > The descriptor can contain a serialized CMD if you need to pass > additional information to the server when you are starting a DoPut > operation. The schema is found in the first RPC message > > FlightInfo contains the "query plan" for accessing a possibly > distributed dataset so really only makes sense for the DoGet RPC. > > Hope this helps > > Wes > > On Fri, May 24, 2019 at 8:18 PM ming zhang <ming.zhang.ch...@gmail.com> > wrote: > > > > hi > > > > wonder how to understand current doput() call. the doget() call pass the > > flightinfo as the parameter. does it makes sense to also pass flightinfo > as > > part of the doput() call? > > > > thanks > > ming >
