This release is a pre-release and may not be stable for production use.
Join us on Slack!
Overview
Feast (Feature Store) is an open source feature store for machine learning. Feast is the fastest path to manage existing infrastructure to productionize analytic data for model training and online inference.
Feast allows ML platform teams to:
- Make features consistently available for training and serving by managing an offline store (to process historical data for scale-out batch scoring or model training), a low-latency online store (to power real-time prediction), and a battle-tested feature server (to serve pre-computed features online).
- Avoid data leakage by generating point-in-time correct feature sets so data scientists can focus on feature engineering rather than debugging error-prone dataset joining logic. This ensure that future feature values do not leak to models during training.
- Decouple ML from data infrastructure by providing a single data access layer that abstracts feature storage from feature retrieval, ensuring models remain portable as you move from training models to serving models, from batch models to realtime models, and from one data infra system to another.
Please see our documentation for more information about the project.
📐 Architecture
The above architecture is the minimal Feast deployment. Want to run the full Feast on Snowflake/GCP/AWS? Click here.
🐣 Getting Started
1. Install Feast
pip install feast
2. Create a feature repository
feast init my_feature_repo
cd my_feature_repo/feature_repo
3. Register your feature definitions and set up your feature store
feast apply
4. Explore your data in the web UI (experimental)
feast ui
5. Build a training dataset
from feast import FeatureStore
import pandas as pd
from datetime import datetime
entity_df = pd.DataFrame.from_dict({
"driver_id": [1001, 1002, 1003, 1004],
"event_timestamp": [
datetime(2021, 4, 12, 10, 59, 42),
datetime(2021, 4, 12, 8, 12, 10),
datetime(2021, 4, 12, 16, 40, 26),
datetime(2021, 4, 12, 15, 1 , 12)
]
})
store = FeatureStore(repo_path=".")
training_df = store.get_historical_features(
entity_df=entity_df,
features = [
'driver_hourly_stats:conv_rate',
'driver_hourly_stats:acc_rate',
'driver_hourly_stats:avg_daily_trips'
],
).to_df()
print(training_df.head())
# Train model
# model = ml.fit(training_df)
event_timestamp driver_id conv_rate acc_rate avg_daily_trips
0 2021-04-12 08:12:10+00:00 1002 0.713465 0.597095 531
1 2021-04-12 10:59:42+00:00 1001 0.072752 0.044344 11
2 2021-04-12 15:01:12+00:00 1004 0.658182 0.079150 220
3 2021-04-12 16:40:26+00:00 1003 0.162092 0.309035 959
6. Load feature values into your online store
Option 1: Incremental materialization (recommended)
CURRENT_TIME=$(date -u +"%Y-%m-%dT%H:%M:%S")
feast materialize-incremental $CURRENT_TIME
Option 2: Full materialization with timestamps
CURRENT_TIME=$(date -u +"%Y-%m-%dT%H:%M:%S")
feast materialize 2021-04-12T00:00:00 $CURRENT_TIME
Option 3: Simple materialization without timestamps
feast materialize --disable-event-timestamp
The --disable-event-timestamp flag allows you to materialize all available feature data using the current datetime as the event timestamp, without needing to specify start and end timestamps. This is useful when your source data lacks proper event timestamp columns.
Materializing feature view driver_hourly_stats from 2021-04-14 to 2021-04-15 done!
7. Read online features at low latency
from pprint import pprint
from feast import FeatureStore
store = FeatureStore(repo_path=".")
feature_vector = store.get_online_features(
features=[
'driver_hourly_stats:conv_rate',
'driver_hourly_stats:acc_rate',
'driver_hourly_stats:avg_daily_trips'
],
entity_rows=[{"driver_id": 1001}]
).to_dict()
pprint(feature_vector)
# Make prediction
# model.predict(feature_vector)
{
"driver_id": [1001],
"driver_hourly_stats__conv_rate": [0.49274],
"driver_hourly_stats__acc_rate": [0.92743],
"driver_hourly_stats__avg_daily_trips": [72]
}
📦 Functionality and Roadmap
The list below contains the functionality that contributors are planning to develop for Feast.
-
We welcome contribution to all items in the roadmap!
-
Natural Language Processing
- Vector Search (Alpha release. See RFC)
- Enhanced Feature Server and SDK for native support for NLP
-
Data Sources
- Snowflake source
- Redshift source
- BigQuery source
- Parquet file source
- Azure Synapse + Azure SQL source (contrib plugin)
- Hive (community plugin)
- Postgres (contrib plugin)
- Spark (contrib plugin)
- Couchbase (contrib plugin)
- Athena (contrib plugin)
- Clickhouse (contrib plugin)
- Oracle (contrib plugin)
- MongoDB (contrib plugin)
- Ray source (contrib plugin)
- Kafka / Kinesis sources (via push support into the online store)
-
Offline Stores
- Snowflake
- Redshift
- BigQuery
- DuckDB
- Dask
- Remote
- Azure Synapse + Azure SQL (contrib plugin)
- Hive (community plugin)
- Postgres (contrib plugin)
- Trino (contrib plugin)
- Spark (contrib plugin)
- Couchbase (contrib plugin)
- Athena (contrib plugin)
- Clickhouse (contrib plugin)
- Ray (contrib plugin)
- Oracle (contrib plugin)
- MongoDB (contrib plugin)
- Hybrid
- Custom offline store support
-
Online Stores
- Snowflake
- DynamoDB
- Redis
- Dragonfly
- Datastore
- Bigtable
- SQLite
- Remote
- Postgres
- HBase
- Cassandra / AstraDB
- ScyllaDB
- MySQL
- Hazelcast
- Elasticsearch
- SingleStore
- Couchbase
- MongoDB
- Aerospike
- Qdrant (vector store)
- Milvus (vector store)
- Faiss (vector store)
- Hybrid
- Azure Cache for Redis (community plugin)
- Custom online store support
-
Feature Engineering
- On-demand Transformations (On Read) (Beta release. See RFC)
- Streaming Transformations (Alpha release. See RFC)
- Batch transformation (In progress. See RFC)
- On-demand Transformations (On Write) (Beta release. See GitHub Issue)
-
Streaming
-
Deployments
-
Feature Serving
-
Data Quality Management (See RFC)
- Feature Quality Monitoring — built-in metrics, drift detection, serving log monitoring, and UI dashboard
-
Feature Discovery and Governance
- Python SDK for browsing feature registry
- CLI for browsing feature registry
- Model-centric feature tracking (feature services)
- Amundsen integration (see Feast extractor)
- DataHub integration (see DataHub Feast docs)
- Feast Web UI (Beta release. See docs)
- Feast Lineage Explorer
🎓 Important Resources
Please refer to the official documentation at Documentation
👋 Contributing
Feast is a community project and is still under active development. Please have a look at our contributing and development guides if you want to contribute to the project:
- Contribution Process for Feast
- Development Guide for Feast
- Development Guide for the Main Feast Repository
🌟 GitHub Star History
✨ Contributors
Thanks goes to these incredible people:
5 maintainers
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file feast-0.66.0.dev59.tar.gz.
File metadata
- Download URL: feast-0.66.0.dev59.tar.gz
- Upload date:
- Size: 8.0 MB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.9.25
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
dde9d9a92a5b31019ef9a6a61c138952514a6f0e0edfe594a67ce8dbfb9f535e
|
|
| MD5 |
df00cd64ccfb4140681489ee670b1927
|
|
| BLAKE2b-256 |
d9916a5930085a8cdd7cde54843956fb7f86667531504becae2cc367b0cc929b
|
File details
Details for the file feast-0.66.0.dev59-py3-none-any.whl.
File metadata
- Download URL: feast-0.66.0.dev59-py3-none-any.whl
- Upload date:
- Size: 9.4 MB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: twine/6.2.0 CPython/3.9.25
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
38fd3bbf9ada1df63f384c3d0c32c9a1e020765e2eec1309a8e4c216c702b514
|
|
| MD5 |
37c472cb026c8352cf546cba5e08a2f7
|
|
| BLAKE2b-256 |
1115213eebdcb8b3269ada3661924516b263327ee351a748ff1fe50de71300b4
|
