Class StructuredQuery.Builder

java.lang.Object
com.google.protobuf.AbstractMessageLite.Builder
com.google.protobuf.AbstractMessage.Builder<BuilderT>
com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
com.google.firestore.v1.StructuredQuery.Builder
All Implemented Interfaces:
StructuredQueryOrBuilder, com.google.protobuf.Message.Builder, com.google.protobuf.MessageLite.Builder, com.google.protobuf.MessageLiteOrBuilder, com.google.protobuf.MessageOrBuilder, Cloneable
Enclosing class:
StructuredQuery

public static final class StructuredQuery.Builder extends com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder> implements StructuredQueryOrBuilder
 A Firestore query.

 The query stages are executed in the following order:
 1. from
 2. where
 3. select
 4. order_by + start_at + end_at
 5. offset
 6. limit
 7. find_nearest
 
Protobuf type google.firestore.v1.StructuredQuery
  • Method Details

    • getDescriptor

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

      protected com.google.protobuf.GeneratedMessageV3.FieldAccessorTable internalGetFieldAccessorTable()
      Specified by:
      internalGetFieldAccessorTable in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • clear

      public StructuredQuery.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.GeneratedMessageV3.Builder<StructuredQuery.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.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • getDefaultInstanceForType

      public StructuredQuery getDefaultInstanceForType()
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageLiteOrBuilder
      Specified by:
      getDefaultInstanceForType in interface com.google.protobuf.MessageOrBuilder
    • build

      public StructuredQuery build()
      Specified by:
      build in interface com.google.protobuf.Message.Builder
      Specified by:
      build in interface com.google.protobuf.MessageLite.Builder
    • buildPartial

      public StructuredQuery buildPartial()
      Specified by:
      buildPartial in interface com.google.protobuf.Message.Builder
      Specified by:
      buildPartial in interface com.google.protobuf.MessageLite.Builder
    • clone

      public StructuredQuery.Builder clone()
      Specified by:
      clone in interface com.google.protobuf.Message.Builder
      Specified by:
      clone in interface com.google.protobuf.MessageLite.Builder
      Overrides:
      clone in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • setField

      public StructuredQuery.Builder setField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      setField in interface com.google.protobuf.Message.Builder
      Overrides:
      setField in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • clearField

      public StructuredQuery.Builder clearField(com.google.protobuf.Descriptors.FieldDescriptor field)
      Specified by:
      clearField in interface com.google.protobuf.Message.Builder
      Overrides:
      clearField in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • clearOneof

      public StructuredQuery.Builder clearOneof(com.google.protobuf.Descriptors.OneofDescriptor oneof)
      Specified by:
      clearOneof in interface com.google.protobuf.Message.Builder
      Overrides:
      clearOneof in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • setRepeatedField

      public StructuredQuery.Builder setRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, int index, Object value)
      Specified by:
      setRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      setRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • addRepeatedField

      public StructuredQuery.Builder addRepeatedField(com.google.protobuf.Descriptors.FieldDescriptor field, Object value)
      Specified by:
      addRepeatedField in interface com.google.protobuf.Message.Builder
      Overrides:
      addRepeatedField in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • mergeFrom

      public StructuredQuery.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<StructuredQuery.Builder>
    • mergeFrom

      public StructuredQuery.Builder mergeFrom(StructuredQuery other)
    • isInitialized

      public final boolean isInitialized()
      Specified by:
      isInitialized in interface com.google.protobuf.MessageLiteOrBuilder
      Overrides:
      isInitialized in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • mergeFrom

      public StructuredQuery.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<StructuredQuery.Builder>
      Throws:
      IOException
    • hasSelect

      public boolean hasSelect()
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
      Specified by:
      hasSelect in interface StructuredQueryOrBuilder
      Returns:
      Whether the select field is set.
    • getSelect

      public StructuredQuery.Projection getSelect()
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
      Specified by:
      getSelect in interface StructuredQueryOrBuilder
      Returns:
      The select.
    • setSelect

       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
    • setSelect

      public StructuredQuery.Builder setSelect(StructuredQuery.Projection.Builder builderForValue)
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
    • mergeSelect

       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
    • clearSelect

      public StructuredQuery.Builder clearSelect()
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
    • getSelectBuilder

      public StructuredQuery.Projection.Builder getSelectBuilder()
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
    • getSelectOrBuilder

      public StructuredQuery.ProjectionOrBuilder getSelectOrBuilder()
       Optional sub-set of the fields to return.
      
       This acts as a [DocumentMask][google.firestore.v1.DocumentMask] over the
       documents returned from a query. When not set, assumes that the caller
       wants all fields returned.
       
      .google.firestore.v1.StructuredQuery.Projection select = 1;
      Specified by:
      getSelectOrBuilder in interface StructuredQueryOrBuilder
    • getFromList

       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
      Specified by:
      getFromList in interface StructuredQueryOrBuilder
    • getFromCount

      public int getFromCount()
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
      Specified by:
      getFromCount in interface StructuredQueryOrBuilder
    • getFrom

      public StructuredQuery.CollectionSelector getFrom(int index)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
      Specified by:
      getFrom in interface StructuredQueryOrBuilder
    • setFrom

      public StructuredQuery.Builder setFrom(int index, StructuredQuery.CollectionSelector value)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • setFrom

      public StructuredQuery.Builder setFrom(int index, StructuredQuery.CollectionSelector.Builder builderForValue)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addFrom

       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addFrom

      public StructuredQuery.Builder addFrom(int index, StructuredQuery.CollectionSelector value)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addFrom

       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addFrom

      public StructuredQuery.Builder addFrom(int index, StructuredQuery.CollectionSelector.Builder builderForValue)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addAllFrom

       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • clearFrom

      public StructuredQuery.Builder clearFrom()
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • removeFrom

      public StructuredQuery.Builder removeFrom(int index)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • getFromBuilder

      public StructuredQuery.CollectionSelector.Builder getFromBuilder(int index)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • getFromOrBuilder

      public StructuredQuery.CollectionSelectorOrBuilder getFromOrBuilder(int index)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
      Specified by:
      getFromOrBuilder in interface StructuredQueryOrBuilder
    • getFromOrBuilderList

      public List<? extends StructuredQuery.CollectionSelectorOrBuilder> getFromOrBuilderList()
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
      Specified by:
      getFromOrBuilderList in interface StructuredQueryOrBuilder
    • addFromBuilder

       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • addFromBuilder

      public StructuredQuery.CollectionSelector.Builder addFromBuilder(int index)
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • getFromBuilderList

      public List<StructuredQuery.CollectionSelector.Builder> getFromBuilderList()
       The collections to query.
       
      repeated .google.firestore.v1.StructuredQuery.CollectionSelector from = 2;
    • hasWhere

      public boolean hasWhere()
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
      Specified by:
      hasWhere in interface StructuredQueryOrBuilder
      Returns:
      Whether the where field is set.
    • getWhere

      public StructuredQuery.Filter getWhere()
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
      Specified by:
      getWhere in interface StructuredQueryOrBuilder
      Returns:
      The where.
    • setWhere

       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
    • setWhere

      public StructuredQuery.Builder setWhere(StructuredQuery.Filter.Builder builderForValue)
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
    • mergeWhere

       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
    • clearWhere

      public StructuredQuery.Builder clearWhere()
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
    • getWhereBuilder

      public StructuredQuery.Filter.Builder getWhereBuilder()
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
    • getWhereOrBuilder

      public StructuredQuery.FilterOrBuilder getWhereOrBuilder()
       The filter to apply.
       
      .google.firestore.v1.StructuredQuery.Filter where = 3;
      Specified by:
      getWhereOrBuilder in interface StructuredQueryOrBuilder
    • getOrderByList

      public List<StructuredQuery.Order> getOrderByList()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
      Specified by:
      getOrderByList in interface StructuredQueryOrBuilder
    • getOrderByCount

      public int getOrderByCount()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
      Specified by:
      getOrderByCount in interface StructuredQueryOrBuilder
    • getOrderBy

      public StructuredQuery.Order getOrderBy(int index)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
      Specified by:
      getOrderBy in interface StructuredQueryOrBuilder
    • setOrderBy

      public StructuredQuery.Builder setOrderBy(int index, StructuredQuery.Order value)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • setOrderBy

      public StructuredQuery.Builder setOrderBy(int index, StructuredQuery.Order.Builder builderForValue)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addOrderBy

       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addOrderBy

      public StructuredQuery.Builder addOrderBy(int index, StructuredQuery.Order value)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addOrderBy

      public StructuredQuery.Builder addOrderBy(StructuredQuery.Order.Builder builderForValue)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addOrderBy

      public StructuredQuery.Builder addOrderBy(int index, StructuredQuery.Order.Builder builderForValue)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addAllOrderBy

      public StructuredQuery.Builder addAllOrderBy(Iterable<? extends StructuredQuery.Order> values)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • clearOrderBy

      public StructuredQuery.Builder clearOrderBy()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • removeOrderBy

      public StructuredQuery.Builder removeOrderBy(int index)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • getOrderByBuilder

      public StructuredQuery.Order.Builder getOrderByBuilder(int index)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • getOrderByOrBuilder

      public StructuredQuery.OrderOrBuilder getOrderByOrBuilder(int index)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
      Specified by:
      getOrderByOrBuilder in interface StructuredQueryOrBuilder
    • getOrderByOrBuilderList

      public List<? extends StructuredQuery.OrderOrBuilder> getOrderByOrBuilderList()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
      Specified by:
      getOrderByOrBuilderList in interface StructuredQueryOrBuilder
    • addOrderByBuilder

      public StructuredQuery.Order.Builder addOrderByBuilder()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • addOrderByBuilder

      public StructuredQuery.Order.Builder addOrderByBuilder(int index)
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • getOrderByBuilderList

      public List<StructuredQuery.Order.Builder> getOrderByBuilderList()
       The order to apply to the query results.
      
       Firestore allows callers to provide a full ordering, a partial ordering, or
       no ordering at all. In all cases, Firestore guarantees a stable ordering
       through the following rules:
      
        * The `order_by` is required to reference all fields used with an
          inequality filter.
        * All fields that are required to be in the `order_by` but are not already
          present are appended in lexicographical ordering of the field name.
        * If an order on `__name__` is not specified, it is appended by default.
      
       Fields are appended with the same sort direction as the last order
       specified, or 'ASCENDING' if no order was specified. For example:
      
        * `ORDER BY a` becomes `ORDER BY a ASC, __name__ ASC`
        * `ORDER BY a DESC` becomes `ORDER BY a DESC, __name__ DESC`
        * `WHERE a > 1` becomes `WHERE a > 1 ORDER BY a ASC, __name__ ASC`
        * `WHERE __name__ > ... AND a > 1` becomes
           `WHERE __name__ > ... AND a > 1 ORDER BY a ASC, __name__ ASC`
       
      repeated .google.firestore.v1.StructuredQuery.Order order_by = 4;
    • hasStartAt

      public boolean hasStartAt()
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
      Specified by:
      hasStartAt in interface StructuredQueryOrBuilder
      Returns:
      Whether the startAt field is set.
    • getStartAt

      public Cursor getStartAt()
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
      Specified by:
      getStartAt in interface StructuredQueryOrBuilder
      Returns:
      The startAt.
    • setStartAt

      public StructuredQuery.Builder setStartAt(Cursor value)
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
    • setStartAt

      public StructuredQuery.Builder setStartAt(Cursor.Builder builderForValue)
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
    • mergeStartAt

      public StructuredQuery.Builder mergeStartAt(Cursor value)
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
    • clearStartAt

      public StructuredQuery.Builder clearStartAt()
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
    • getStartAtBuilder

      public Cursor.Builder getStartAtBuilder()
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
    • getStartAtOrBuilder

      public CursorOrBuilder getStartAtOrBuilder()
       A potential prefix of a position in the result set to start the query at.
      
       The ordering of the result set is based on the `ORDER BY` clause of the
       original query.
      
       ```
       SELECT * FROM k WHERE a = 1 AND b > 2 ORDER BY b ASC, __name__ ASC;
       ```
      
       This query's results are ordered by `(b ASC, __name__ ASC)`.
      
       Cursors can reference either the full ordering or a prefix of the location,
       though it cannot reference more fields than what are in the provided
       `ORDER BY`.
      
       Continuing off the example above, attaching the following start cursors
       will have varying impact:
      
       - `START BEFORE (2, /k/123)`: start the query right before `a = 1 AND
          b > 2 AND __name__ > /k/123`.
       - `START AFTER (10)`: start the query right after `a = 1 AND b > 10`.
      
       Unlike `OFFSET` which requires scanning over the first N results to skip,
       a start cursor allows the query to begin at a logical position. This
       position is not required to match an actual result, it will scan forward
       from this position to find the next document.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor start_at = 7;
      Specified by:
      getStartAtOrBuilder in interface StructuredQueryOrBuilder
    • hasEndAt

      public boolean hasEndAt()
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
      Specified by:
      hasEndAt in interface StructuredQueryOrBuilder
      Returns:
      Whether the endAt field is set.
    • getEndAt

      public Cursor getEndAt()
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
      Specified by:
      getEndAt in interface StructuredQueryOrBuilder
      Returns:
      The endAt.
    • setEndAt

      public StructuredQuery.Builder setEndAt(Cursor value)
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
    • setEndAt

      public StructuredQuery.Builder setEndAt(Cursor.Builder builderForValue)
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
    • mergeEndAt

      public StructuredQuery.Builder mergeEndAt(Cursor value)
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
    • clearEndAt

      public StructuredQuery.Builder clearEndAt()
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
    • getEndAtBuilder

      public Cursor.Builder getEndAtBuilder()
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
    • getEndAtOrBuilder

      public CursorOrBuilder getEndAtOrBuilder()
       A potential prefix of a position in the result set to end the query at.
      
       This is similar to `START_AT` but with it controlling the end position
       rather than the start position.
      
       Requires:
      
       * The number of values cannot be greater than the number of fields
         specified in the `ORDER BY` clause.
       
      .google.firestore.v1.Cursor end_at = 8;
      Specified by:
      getEndAtOrBuilder in interface StructuredQueryOrBuilder
    • getOffset

      public int getOffset()
       The number of documents to skip before returning the first result.
      
       This applies after the constraints specified by the `WHERE`, `START AT`, &
       `END AT` but before the `LIMIT` clause.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      int32 offset = 6;
      Specified by:
      getOffset in interface StructuredQueryOrBuilder
      Returns:
      The offset.
    • setOffset

      public StructuredQuery.Builder setOffset(int value)
       The number of documents to skip before returning the first result.
      
       This applies after the constraints specified by the `WHERE`, `START AT`, &
       `END AT` but before the `LIMIT` clause.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      int32 offset = 6;
      Parameters:
      value - The offset to set.
      Returns:
      This builder for chaining.
    • clearOffset

      public StructuredQuery.Builder clearOffset()
       The number of documents to skip before returning the first result.
      
       This applies after the constraints specified by the `WHERE`, `START AT`, &
       `END AT` but before the `LIMIT` clause.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      int32 offset = 6;
      Returns:
      This builder for chaining.
    • hasLimit

      public boolean hasLimit()
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
      Specified by:
      hasLimit in interface StructuredQueryOrBuilder
      Returns:
      Whether the limit field is set.
    • getLimit

      public com.google.protobuf.Int32Value getLimit()
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
      Specified by:
      getLimit in interface StructuredQueryOrBuilder
      Returns:
      The limit.
    • setLimit

      public StructuredQuery.Builder setLimit(com.google.protobuf.Int32Value value)
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
    • setLimit

      public StructuredQuery.Builder setLimit(com.google.protobuf.Int32Value.Builder builderForValue)
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
    • mergeLimit

      public StructuredQuery.Builder mergeLimit(com.google.protobuf.Int32Value value)
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
    • clearLimit

      public StructuredQuery.Builder clearLimit()
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
    • getLimitBuilder

      public com.google.protobuf.Int32Value.Builder getLimitBuilder()
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
    • getLimitOrBuilder

      public com.google.protobuf.Int32ValueOrBuilder getLimitOrBuilder()
       The maximum number of results to return.
      
       Applies after all other constraints.
      
       Requires:
      
       * The value must be greater than or equal to zero if specified.
       
      .google.protobuf.Int32Value limit = 5;
      Specified by:
      getLimitOrBuilder in interface StructuredQueryOrBuilder
    • hasFindNearest

      public boolean hasFindNearest()
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
      Specified by:
      hasFindNearest in interface StructuredQueryOrBuilder
      Returns:
      Whether the findNearest field is set.
    • getFindNearest

      public StructuredQuery.FindNearest getFindNearest()
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
      Specified by:
      getFindNearest in interface StructuredQueryOrBuilder
      Returns:
      The findNearest.
    • setFindNearest

       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
    • setFindNearest

      public StructuredQuery.Builder setFindNearest(StructuredQuery.FindNearest.Builder builderForValue)
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
    • mergeFindNearest

      public StructuredQuery.Builder mergeFindNearest(StructuredQuery.FindNearest value)
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
    • clearFindNearest

      public StructuredQuery.Builder clearFindNearest()
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
    • getFindNearestBuilder

      public StructuredQuery.FindNearest.Builder getFindNearestBuilder()
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
    • getFindNearestOrBuilder

      public StructuredQuery.FindNearestOrBuilder getFindNearestOrBuilder()
       Optional. A potential nearest neighbors search.
      
       Applies after all other filters and ordering.
      
       Finds the closest vector embeddings to the given query vector.
       
      .google.firestore.v1.StructuredQuery.FindNearest find_nearest = 9 [(.google.api.field_behavior) = OPTIONAL];
      Specified by:
      getFindNearestOrBuilder in interface StructuredQueryOrBuilder
    • setUnknownFields

      public final StructuredQuery.Builder setUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      setUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      setUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>
    • mergeUnknownFields

      public final StructuredQuery.Builder mergeUnknownFields(com.google.protobuf.UnknownFieldSet unknownFields)
      Specified by:
      mergeUnknownFields in interface com.google.protobuf.Message.Builder
      Overrides:
      mergeUnknownFields in class com.google.protobuf.GeneratedMessageV3.Builder<StructuredQuery.Builder>