Trait arrow_flight::flight_service_server::FlightService

source · 
pub trait FlightService: Send + Sync + 'static {
    type HandshakeStream: Stream<Item = Result<HandshakeResponse, Status>> + Send + 'static;
    type ListFlightsStream: Stream<Item = Result<FlightInfo, Status>> + Send + 'static;
    type DoGetStream: Stream<Item = Result<FlightData, Status>> + Send + 'static;
    type DoPutStream: Stream<Item = Result<PutResult, Status>> + Send + 'static;
    type DoExchangeStream: Stream<Item = Result<FlightData, Status>> + Send + 'static;
    type DoActionStream: Stream<Item = Result<Result, Status>> + Send + 'static;
    type ListActionsStream: Stream<Item = Result<ActionType, Status>> + Send + 'static;

    fn handshake<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Streaming<HandshakeRequest>>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::HandshakeStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn list_flights<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Criteria>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::ListFlightsStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn get_flight_info<'life0, 'async_trait>(
        &'life0 self,
        request: Request<FlightDescriptor>
    ) -> Pin<Box<dyn Future<Output = Result<Response<FlightInfo>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn get_schema<'life0, 'async_trait>(
        &'life0 self,
        request: Request<FlightDescriptor>
    ) -> Pin<Box<dyn Future<Output = Result<Response<SchemaResult>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn do_get<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Ticket>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::DoGetStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn do_put<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Streaming<FlightData>>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::DoPutStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn do_exchange<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Streaming<FlightData>>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::DoExchangeStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn do_action<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Action>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::DoActionStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
    fn list_actions<'life0, 'async_trait>(
        &'life0 self,
        request: Request<Empty>
    ) -> Pin<Box<dyn Future<Output = Result<Response<Self::ListActionsStream>, Status>> + Send + 'async_trait>>
    where
        Self: 'async_trait,
        'life0: 'async_trait;
}
Expand description

Generated trait containing gRPC methods that should be implemented for use with FlightServiceServer.

Required Associated Types§

Server streaming response type for the Handshake method.

Server streaming response type for the ListFlights method.

Server streaming response type for the DoGet method.

Server streaming response type for the DoPut method.

Server streaming response type for the DoExchange method.

Server streaming response type for the DoAction method.

Server streaming response type for the ListActions method.

Required Methods§

Handshake between client and server. Depending on the server, the handshake may be required to determine the token that should be used for future operations. Both request and response are streams to allow multiple round-trips depending on auth mechanism.

Get a list of available streams given a particular criteria. Most flight services will expose one or more streams that are readily available for retrieval. This api allows listing the streams available for consumption. A user can also provide a criteria. The criteria can limit the subset of streams that can be listed via this interface. Each flight service allows its own definition of how to consume criteria.

For a given FlightDescriptor, get information about how the flight can be consumed. This is a useful interface if the consumer of the interface already can identify the specific flight to consume. This interface can also allow a consumer to generate a flight stream through a specified descriptor. For example, a flight descriptor might be something that includes a SQL statement or a Pickled Python operation that will be executed. In those cases, the descriptor will not be previously available within the list of available streams provided by ListFlights but will be available for consumption for the duration defined by the specific flight service.

For a given FlightDescriptor, get the Schema as described in Schema.fbs::Schema This is used when a consumer needs the Schema of flight stream. Similar to GetFlightInfo this interface may generate a new flight that was not previously available in ListFlights.

Retrieve a single stream associated with a particular descriptor associated with the referenced ticket. A Flight can be composed of one or more streams where each stream can be retrieved using a separate opaque ticket that the flight service uses for managing a collection of streams.

Push a stream to the flight service associated with a particular flight stream. This allows a client of a flight service to upload a stream of data. Depending on the particular flight service, a client consumer could be allowed to upload a single stream per descriptor or an unlimited number. In the latter, the service might implement a ‘seal’ action that can be applied to a descriptor once all streams are uploaded.

Open a bidirectional data channel for a given descriptor. This allows clients to send and receive arbitrary Arrow data and application-specific metadata in a single logical stream. In contrast to DoGet/DoPut, this is more suited for clients offloading computation (rather than storage) to a Flight service.

Flight services can support an arbitrary number of simple actions in addition to the possible ListFlights, GetFlightInfo, DoGet, DoPut operations that are potentially available. DoAction allows a flight client to do a specific action against a flight service. An action includes opaque request and response objects that are specific to the type action being undertaken.

A flight service exposes all of the available action types that it has along with descriptions. This allows different flight consumers to understand the capabilities of the flight service.

Implementors§

Implements the lower level interface to handle FlightSQL