Class FeaturestoreServiceGrpc.FeaturestoreServiceBlockingStub

    • Method Detail

      • createFeaturestore

        public com.google.longrunning.Operation createFeaturestore​(CreateFeaturestoreRequest request)
         Creates a new Featurestore in a given project and location.
         
      • updateFeaturestore

        public com.google.longrunning.Operation updateFeaturestore​(UpdateFeaturestoreRequest request)
         Updates the parameters of a single Featurestore.
         
      • deleteFeaturestore

        public com.google.longrunning.Operation deleteFeaturestore​(DeleteFeaturestoreRequest request)
         Deletes a single Featurestore. The Featurestore must not contain any
         EntityTypes or `force` must be set to true for the request to succeed.
         
      • createEntityType

        public com.google.longrunning.Operation createEntityType​(CreateEntityTypeRequest request)
         Creates a new EntityType in a given Featurestore.
         
      • deleteEntityType

        public com.google.longrunning.Operation deleteEntityType​(DeleteEntityTypeRequest request)
         Deletes a single EntityType. The EntityType must not have any Features
         or `force` must be set to true for the request to succeed.
         
      • createFeature

        public com.google.longrunning.Operation createFeature​(CreateFeatureRequest request)
         Creates a new Feature in a given EntityType.
         
      • batchCreateFeatures

        public com.google.longrunning.Operation batchCreateFeatures​(BatchCreateFeaturesRequest request)
         Creates a batch of Features in a given EntityType.
         
      • deleteFeature

        public com.google.longrunning.Operation deleteFeature​(DeleteFeatureRequest request)
         Deletes a single Feature.
         
      • importFeatureValues

        public com.google.longrunning.Operation importFeatureValues​(ImportFeatureValuesRequest request)
         Imports Feature values into the Featurestore from a source storage.
         The progress of the import is tracked by the returned operation. The
         imported features are guaranteed to be visible to subsequent read
         operations after the operation is marked as successfully done.
         If an import operation fails, the Feature values returned from
         reads and exports may be inconsistent. If consistency is
         required, the caller must retry the same import request again and wait till
         the new operation returned is marked as successfully done.
         There are also scenarios where the caller can cause inconsistency.
          - Source data for import contains multiple distinct Feature values for
            the same entity ID and timestamp.
          - Source is modified during an import. This includes adding, updating, or
          removing source data and/or metadata. Examples of updating metadata
          include but are not limited to changing storage location, storage class,
          or retention policy.
          - Online serving cluster is under-provisioned.
         
      • batchReadFeatureValues

        public com.google.longrunning.Operation batchReadFeatureValues​(BatchReadFeatureValuesRequest request)
         Batch reads Feature values from a Featurestore.
         This API enables batch reading Feature values, where each read
         instance in the batch may read Feature values of entities from one or
         more EntityTypes. Point-in-time correctness is guaranteed for Feature
         values of each read instance as of each instance's read timestamp.
         
      • exportFeatureValues

        public com.google.longrunning.Operation exportFeatureValues​(ExportFeatureValuesRequest request)
         Exports Feature values from all the entities of a target EntityType.
         
      • deleteFeatureValues

        public com.google.longrunning.Operation deleteFeatureValues​(DeleteFeatureValuesRequest request)
         Delete Feature values from Featurestore.
         The progress of the deletion is tracked by the returned operation. The
         deleted feature values are guaranteed to be invisible to subsequent read
         operations after the operation is marked as successfully done.
         If a delete feature values operation fails, the feature values
         returned from reads and exports may be inconsistent. If consistency is
         required, the caller must retry the same delete request again and wait till
         the new operation returned is marked as successfully done.