Feature repository

Feast users use Feast to manage two important sets of configuration:
Configuration about how to run Feast on your infrastructure
Feature definitions
With Feast, the above configuration can be written declaratively and stored as code in a central location. This central location is called a feature repository. The feature repository is the declarative source of truth for what the desired state of a feature store should be.
The Feast CLI uses the feature repository to configure, deploy, and manage your feature store.
An example structure of a feature repository is shown below:
1
$ tree -a
2
.
3
├── data
4
│   └── driver_stats.parquet
5
├── driver_features.py
6
├── feature_store.yaml
7
└── .feastignore
8
​
9
1 directory, 4 files
Copied!
For more details, see the Feature repository reference.

Overview

Registry

Last modified 7d ago

Export as PDF

Copy link

Edit on GitHub