Chapter 7. Feature Store command line interface reference

• Scans definitions

  Scans the Python files in the feature repository to identify Feature Store object definitions. This includes feature views, entities, and data sources.

• Validates definitions

  Validates feature definitions to ensure accuracy.

• Synchronizes metadata

  Synchronizes the metadata of Feature Store objects in the registry. If a registry does not exist, the Feature Store creates one. The standard registry is a protobuf binary file stored on a disk, either locally or in an object store.

• Provisions infrastructure

  Creates the necessary Feature Store infrastructure. The deployed infrastructure depends on the provider configuration specified in the feature_store.yaml file:

  • Local provider: Creates a SQLite online store.

  • Cloud provider: Creates cloud infrastructure for services such as Google Cloud Platform (GCP) or Amazon Web Services (AWS).

    Note

    Creating cloud infrastructure might incur costs.

Delete command examples

• Delete a feature view named driver_hourly_stats:

  feast delete driver_hourly_stats

• Delete an entity named driver:

  feast delete driver

Init examples

• Create a repository with the default template

  The following command creates a repository named my_repo_name:

  $ feast init my_repo_name

  Init output

  Creating a new Feast repository in /projects/my_repo_name.
  
  .
  ├── data
  │   └── driver_stats.parquet
  ├── example.py
  └── feature_store.yaml

• Create a repository using the Google Cloud Platform (GCP) template:

  $ feast init -t gcp my_feature_repo

• Set the name of the new project:

  $ feast init -t gcp my_feature_repo

• The end date of the previous materialization interval.
• The beginning of available history (if no previous materialization exists).