Module org.apache.arrow.flight.core
Package org.apache.arrow.flight.impl

Class Flight.FlightInfo.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder>
org.apache.arrow.flight.impl.Flight.FlightInfo.Builder
All Implemented Interfaces:
com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable, Flight.FlightInfoOrBuilder
Enclosing class:
Flight.FlightInfo
public static final class Flight.FlightInfo.Builder extends com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder> implements Flight.FlightInfoOrBuilder

 The access coordinates for retrieval of a dataset. With a FlightInfo, a
 consumer is able to determine how to retrieve a dataset.
Protobuf type arrow.flight.protocol.FlightInfo

  • Method Details

    • getDescriptor

      public static final com.google.protobuf.Descriptors.Descriptor getDescriptor()

    • internalGetFieldAccessorTable

      protected com.google.protobuf.GeneratedMessage.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder>

    • clear

      public Flight.FlightInfo.Builder clear()
      Specified by:
      clear in interface com.google.protobuf.Message.Builder
      Specified by:
      clear in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clear in class com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder>

    • getDescriptorForType

      public com.google.protobuf.Descriptors.Descriptor getDescriptorForType()
      Specified by:
      getDescriptorForType in interface com.google.protobuf.Message.Builder
      Specified by:
      getDescriptorForType in interface com.google.protobuf.MessageOrBuilder
      Overrides:
      getDescriptorForType in class com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder>

    • getDefaultInstanceForType

      public Flight.FlightInfo getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder

    • build

      public Flight.FlightInfo build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder

    • buildPartial

      public Flight.FlightInfo buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder

    • mergeFrom

      public Flight.FlightInfo.Builder mergeFrom(com.google.protobuf.Message other)
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Flight.FlightInfo.Builder>

    • mergeFrom

      public Flight.FlightInfo.Builder mergeFrom(Flight.FlightInfo other)

    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessage.Builder<Flight.FlightInfo.Builder>

    • mergeFrom

      public Flight.FlightInfo.Builder mergeFrom(com.google.protobuf.CodedInputStream input, com.google.protobuf.ExtensionRegistryLite extensionRegistry) throws IOException
      Specified by:
      mergeFrom in interface com.google.protobuf.Message.Builder
      Specified by:
      mergeFrom in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      mergeFrom in class com.google.protobuf.AbstractMessage.Builder<Flight.FlightInfo.Builder>
      Throws:
      IOException

    • getSchema

      public com.google.protobuf.ByteString getSchema()
       The schema of the dataset in its IPC form:
 4 bytes - an optional IPC_CONTINUATION_TOKEN prefix
 4 bytes - the byte length of the payload
 a flatbuffer Message whose header is the Schema
      bytes schema = 1;
      Specified by:
      getSchema in interface Flight.FlightInfoOrBuilder
      Returns:
      The schema.

    • setSchema

      public Flight.FlightInfo.Builder setSchema(com.google.protobuf.ByteString value)
       The schema of the dataset in its IPC form:
 4 bytes - an optional IPC_CONTINUATION_TOKEN prefix
 4 bytes - the byte length of the payload
 a flatbuffer Message whose header is the Schema
      bytes schema = 1;
      Parameters:
      value - The schema to set.
      Returns:
      This builder for chaining.

    • clearSchema

      public Flight.FlightInfo.Builder clearSchema()
       The schema of the dataset in its IPC form:
 4 bytes - an optional IPC_CONTINUATION_TOKEN prefix
 4 bytes - the byte length of the payload
 a flatbuffer Message whose header is the Schema
      bytes schema = 1;
      Returns:
      This builder for chaining.

    • hasFlightDescriptor

      public boolean hasFlightDescriptor()
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;
      Specified by:
      hasFlightDescriptor in interface Flight.FlightInfoOrBuilder
      Returns:
      Whether the flightDescriptor field is set.

    • getFlightDescriptor

      public Flight.FlightDescriptor getFlightDescriptor()
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;
      Specified by:
      getFlightDescriptor in interface Flight.FlightInfoOrBuilder
      Returns:
      The flightDescriptor.

    • setFlightDescriptor

      public Flight.FlightInfo.Builder setFlightDescriptor(Flight.FlightDescriptor value)
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;

    • setFlightDescriptor

      public Flight.FlightInfo.Builder setFlightDescriptor(Flight.FlightDescriptor.Builder builderForValue)
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;

    • mergeFlightDescriptor

      public Flight.FlightInfo.Builder mergeFlightDescriptor(Flight.FlightDescriptor value)
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;

    • clearFlightDescriptor

      public Flight.FlightInfo.Builder clearFlightDescriptor()
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;

    • getFlightDescriptorBuilder

      public Flight.FlightDescriptor.Builder getFlightDescriptorBuilder()
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;

    • getFlightDescriptorOrBuilder

      public Flight.FlightDescriptorOrBuilder getFlightDescriptorOrBuilder()
      
 The descriptor associated with this info.
      .arrow.flight.protocol.FlightDescriptor flight_descriptor = 2;
      Specified by:
      getFlightDescriptorOrBuilder in interface Flight.FlightInfoOrBuilder

    • getEndpointList

      public List<Flight.FlightEndpoint> getEndpointList()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;
      Specified by:
      getEndpointList in interface Flight.FlightInfoOrBuilder

    • getEndpointCount

      public int getEndpointCount()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;
      Specified by:
      getEndpointCount in interface Flight.FlightInfoOrBuilder

    • getEndpoint

      public Flight.FlightEndpoint getEndpoint(int index)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;
      Specified by:
      getEndpoint in interface Flight.FlightInfoOrBuilder

    • setEndpoint

      public Flight.FlightInfo.Builder setEndpoint(int index, Flight.FlightEndpoint value)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • setEndpoint

      public Flight.FlightInfo.Builder setEndpoint(int index, Flight.FlightEndpoint.Builder builderForValue)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addEndpoint

      public Flight.FlightInfo.Builder addEndpoint(Flight.FlightEndpoint value)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addEndpoint

      public Flight.FlightInfo.Builder addEndpoint(int index, Flight.FlightEndpoint value)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addEndpoint

      public Flight.FlightInfo.Builder addEndpoint(Flight.FlightEndpoint.Builder builderForValue)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addEndpoint

      public Flight.FlightInfo.Builder addEndpoint(int index, Flight.FlightEndpoint.Builder builderForValue)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addAllEndpoint

      public Flight.FlightInfo.Builder addAllEndpoint(Iterable<? extends Flight.FlightEndpoint> values)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • clearEndpoint

      public Flight.FlightInfo.Builder clearEndpoint()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • removeEndpoint

      public Flight.FlightInfo.Builder removeEndpoint(int index)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • getEndpointBuilder

      public Flight.FlightEndpoint.Builder getEndpointBuilder(int index)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • getEndpointOrBuilder

      public Flight.FlightEndpointOrBuilder getEndpointOrBuilder(int index)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;
      Specified by:
      getEndpointOrBuilder in interface Flight.FlightInfoOrBuilder

    • getEndpointOrBuilderList

      public List<? extends Flight.FlightEndpointOrBuilder> getEndpointOrBuilderList()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;
      Specified by:
      getEndpointOrBuilderList in interface Flight.FlightInfoOrBuilder

    • addEndpointBuilder

      public Flight.FlightEndpoint.Builder addEndpointBuilder()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • addEndpointBuilder

      public Flight.FlightEndpoint.Builder addEndpointBuilder(int index)
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • getEndpointBuilderList

      public List<Flight.FlightEndpoint.Builder> getEndpointBuilderList()
      
 A list of endpoints associated with the flight. To consume the
 whole flight, all endpoints (and hence all Tickets) must be
 consumed. Endpoints can be consumed in any order.

 In other words, an application can use multiple endpoints to
 represent partitioned data.

 If the returned data has an ordering, an application can use
 "FlightInfo.ordered = true" or should return the all data in a
 single endpoint. Otherwise, there is no ordering defined on
 endpoints or the data within.

 A client can read ordered data by reading data from returned
 endpoints, in order, from front to back.

 Note that a client may ignore "FlightInfo.ordered = true". If an
 ordering is important for an application, an application must
 choose one of them:

 * An application requires that all clients must read data in
 returned endpoints order.
 * An application must return the all data in a single endpoint.
      repeated .arrow.flight.protocol.FlightEndpoint endpoint = 3;

    • getTotalRecords

      public long getTotalRecords()
       Set these to -1 if unknown.
      int64 total_records = 4;
      Specified by:
      getTotalRecords in interface Flight.FlightInfoOrBuilder
      Returns:
      The totalRecords.

    • setTotalRecords

      public Flight.FlightInfo.Builder setTotalRecords(long value)
       Set these to -1 if unknown.
      int64 total_records = 4;
      Parameters:
      value - The totalRecords to set.
      Returns:
      This builder for chaining.

    • clearTotalRecords

      public Flight.FlightInfo.Builder clearTotalRecords()
       Set these to -1 if unknown.
      int64 total_records = 4;
      Returns:
      This builder for chaining.

    • getTotalBytes

      public long getTotalBytes()
      int64 total_bytes = 5;
      Specified by:
      getTotalBytes in interface Flight.FlightInfoOrBuilder
      Returns:
      The totalBytes.

    • setTotalBytes

      public Flight.FlightInfo.Builder setTotalBytes(long value)
      int64 total_bytes = 5;
      Parameters:
      value - The totalBytes to set.
      Returns:
      This builder for chaining.

    • clearTotalBytes

      public Flight.FlightInfo.Builder clearTotalBytes()
      int64 total_bytes = 5;
      Returns:
      This builder for chaining.

    • getOrdered

      public boolean getOrdered()
      
 FlightEndpoints are in the same order as the data.
      bool ordered = 6;
      Specified by:
      getOrdered in interface Flight.FlightInfoOrBuilder
      Returns:
      The ordered.

    • setOrdered

      public Flight.FlightInfo.Builder setOrdered(boolean value)
      
 FlightEndpoints are in the same order as the data.
      bool ordered = 6;
      Parameters:
      value - The ordered to set.
      Returns:
      This builder for chaining.

    • clearOrdered

      public Flight.FlightInfo.Builder clearOrdered()
      
 FlightEndpoints are in the same order as the data.
      bool ordered = 6;
      Returns:
      This builder for chaining.

    • getAppMetadata

      public com.google.protobuf.ByteString getAppMetadata()
      
 Application-defined metadata.

 There is no inherent or required relationship between this
 and the app_metadata fields in the FlightEndpoints or resulting
 FlightData messages. Since this metadata is application-defined,
 a given application could define there to be a relationship,
 but there is none required by the spec.
      bytes app_metadata = 7;
      Specified by:
      getAppMetadata in interface Flight.FlightInfoOrBuilder
      Returns:
      The appMetadata.

    • setAppMetadata

      public Flight.FlightInfo.Builder setAppMetadata(com.google.protobuf.ByteString value)
      
 Application-defined metadata.

 There is no inherent or required relationship between this
 and the app_metadata fields in the FlightEndpoints or resulting
 FlightData messages. Since this metadata is application-defined,
 a given application could define there to be a relationship,
 but there is none required by the spec.
      bytes app_metadata = 7;
      Parameters:
      value - The appMetadata to set.
      Returns:
      This builder for chaining.

    • clearAppMetadata

      public Flight.FlightInfo.Builder clearAppMetadata()
      
 Application-defined metadata.

 There is no inherent or required relationship between this
 and the app_metadata fields in the FlightEndpoints or resulting
 FlightData messages. Since this metadata is application-defined,
 a given application could define there to be a relationship,
 but there is none required by the spec.
      bytes app_metadata = 7;
      Returns:
      This builder for chaining.