I'm won't be around much the next couple weeks to help, but this change should be voted on soon so that the implementations can get refactored sooner rather than later
On Thu, Apr 4, 2019 at 2:59 PM Wes McKinney <wesmck...@gmail.com> wrote: > > hi Brian, > > I would guess that ListFlights would mainly return named datasets > having a particular PATH per > > https://github.com/apache/arrow/blob/master/format/Flight.proto#L176 > > Presumably if a server provides support for the CMD-type > FlightDescriptor, that they would have agreed on a .proto or other > serialization format for their commands. > > Shall we put this one to a vote? > > Thanks > > On Thu, Apr 4, 2019 at 11:29 AM Bryan Cutler <cutl...@gmail.com> wrote: > > > > This sounds good to me, but if the FlightDescriptors are opaque commands, > > e.g. protobufs, will the client have to parse a bunch of unknown commands > > in order to find the right one? > > > > On Wed, Apr 3, 2019 at 9:20 AM Jacques Nadeau <jacq...@apache.org> wrote: > > > > > > > > > > Can you explain what you call "splits"? > > > > > > > > > > Per Wes's comments, FlightItineraries inside FlightGetInfo. > > > > > > also is it possible a service have tons of flights? > > > > > > > > > Yes > > > > > > > > > > if so, some kind of > > > > pagination need to be done here? > > > > > > > > > Criteria and the stream interface should be sufficient. We need to work on > > > a formal definition of what criteria means generically. > > >
