.. Licensed to the Apache Software Foundation (ASF) under one .. or more contributor license agreements. See the NOTICE file .. distributed with this work for additional information .. regarding copyright ownership. The ASF licenses this file .. to you under the Apache License, Version 2.0 (the .. "License"); you may not use this file except in compliance .. with the License. You may obtain a copy of the License at .. http://www.apache.org/licenses/LICENSE-2.0 .. Unless required by applicable law or agreed to in writing, .. software distributed under the License is distributed on an .. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY .. KIND, either express or implied. See the License for the .. specific language governing permissions and limitations .. under the License. .. default-domain:: cpp .. highlight:: cpp ================ Arrow Flight RPC ================ Arrow Flight is an RPC framework for efficient transfer of Flight data over the network. See :doc:`../format/Flight` for full details on the protocol, or :doc:`./api/flight` for API docs. Writing a Flight Service ======================== Servers are subclasses of :class:`arrow::flight::FlightServerBase`. To implement individual RPCs, override the RPC methods on this class. .. code-block:: cpp class MyFlightServer : public FlightServerBase { Status ListFlights(const ServerCallContext& context, const Criteria* criteria, std::unique_ptr* listings) override { std::vector flights = ...; *listings = std::unique_ptr(new SimpleFlightListing(flights)); return Status::OK(); } }; Each RPC method always takes a :class:`arrow::flight::ServerCallContext` for common parameters and returns a :class:`arrow::Status` to indicate success or failure. Flight-specific error codes can be returned via :func:`arrow::flight::MakeFlightError`. RPC methods that return a value in addition to a status will use an out parameter, as shown above. Often, there are helper classes providing basic implementations of these out parameters. For instance, above, :class:`arrow::flight::SimpleFlightListing` uses a vector of :class:`arrow::flight::FlightInfo` objects as the result of a ``ListFlights`` RPC. To start a server, create a :class:`arrow::flight::Location` to specify where to listen, and call :func:`arrow::flight::FlightServerBase::Init`. This will start the server, but won't block the rest of the program. Use :func:`arrow::flight::FlightServerBase::SetShutdownOnSignals` to enable stopping the server if an interrupt signal is received, then call :func:`arrow::flight::FlightServerBase::Serve` to block until the server stops. .. code-block:: cpp std::unique_ptr server; // Initialize server arrow::flight::Location location; // Listen to all interfaces on a free port ARROW_CHECK_OK(arrow::flight::Location::ForGrpcTcp("0.0.0.0", 0, &location)); arrow::flight::FlightServerOptions options(location); // Start the server ARROW_CHECK_OK(server->Init(options)); // Exit with a clean error code (0) on SIGTERM ARROW_CHECK_OK(server->SetShutdownOnSignals({SIGTERM})); std::cout << "Server listening on localhost:" << server->port() << std::endl; ARROW_CHECK_OK(server->Serve()); Enabling TLS and Authentication ------------------------------- TLS can be enabled by providing a certificate and key pair to :func:`FlightServerBase::Init `. Additionally, use :func:`Location::ForGrpcTls ` to construct the :class:`arrow::flight::Location` to listen on. Similarly, authentication can be enabled by providing an implementation of :class:`ServerAuthHandler `. Authentication consists of two parts: on initial client connection, the server and client authentication implementations can perform any negotiation needed; then, on each RPC thereafter, the client provides a token. The server authentication handler validates the token and provides the identity of the client. This identity can be obtained from the :class:`arrow::flight::ServerCallContext`. Using the Flight Client ======================= To connect to a Flight service, create an instance of :class:`arrow::flight::FlightClient` by calling :func:`Connect `. This takes a Location and returns the client through an out parameter. To authenticate, call :func:`Authenticate ` with the desired client authentication implementation. Each RPC method returns :class:`arrow::Status` to indicate the success/failure of the request. Any other return values are specified through out parameters. They also take an optional :class:`options ` parameter that allows specifying a timeout for the call.