arrow-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ming zhang <ming.zhang.ch...@gmail.com>
Subject Re: How to understand this comment
Date Wed, 03 Apr 2019 03:07:54 GMT
in a case where there are multiple ways to retrieve this logical data set,
how to represent this in the response?

for example, assume there is a data set that has
part 1 in endpoint 1 and part 2 in endpoint 2 with tcp as transport
both part 1 and part 2 in endpoint 3, with infiniband as transport

now how we return this back to client so client decide which one to consume?

the mental model i have with FightService is similar to travel with flight.

- a travel agency lists many travel choices.
- for a trip from NYC to SFO, there are different itinerary, like NYC->SFO
directly. NYC->Chicago -> SFO, and so on.
- for each itinerary, there could be one or more logical parts (hop)
- for each hop, there are different ways, like business class, economic
class, etc
- they all need a ticket to finish the trip.

is this right, or way off?

Thanks
Ming


On Tue, Apr 2, 2019 at 9:59 PM Wes McKinney <wesmckinn@gmail.com> wrote:

> Hi,
>
> A FlightGetInfo plan corresponds to a single logical dataset. The
> dataset may be spread across multiple endpoints, so if you want the
> whole dataset you have to execute DoGet against them all.
>
> I'm not sure what you mean by "provide more than one execution plan".
>
> - Wes
>
> On Tue, Apr 2, 2019 at 7:54 PM ming zhang <ming.zhang.china@gmail.com>
> wrote:
> >
> > Hi All
> >
> > Wonder how to understand this comment?
> >
> > Looks like this assume we only have one "itinerary" and finish it need to
> > consume all the flight endpoints.
> >
> >   /*
> >    * A list of endpoints associated with the flight. To consume the whole
> >    * flight, all endpoints must be consumed.
> >    */
> >
> > What if we do want to provide more than one execution plan (itinerary)
> and
> > each have multiple steps?
> >
> > Thanks
> > Ming
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message