Search…
master
Introduction
Community
Roadmap
Changelog
Getting started
Quickstart
Concepts
Overview
Data source
Entity
Feature view
Feature service
Feature retrieval
Point-in-time joins
Architecture
Third party integrations
FAQ
Tutorials
Overview
Driver ranking
Fraud detection on GCP
Real-time credit scoring on AWS
How-to Guides
Running Feast with GCP/AWS
Running Feast in production
Upgrading from Feast 0.9
Adding a custom provider
Adding a new online store
Adding a new offline store
Adding or reusing tests
Reference
Data sources
Offline stores
Online stores
Providers
Feature repository
[Alpha] On demand feature view
[Alpha] Stream ingestion
[Alpha] Local feature server
[Alpha] AWS Lambda feature server
Feast CLI reference
Python API reference
Usage
Project
Contribution process
Development guide
Versioning policy
Release process
Feast 0.9 vs Feast 0.10+
Powered By GitBook
Overview
The top-level namespace within Feast is a project. Users define one or more feature views within a project. Each feature view contains one or more features. These features typically relate to one or more entities. A feature view must always have a data source, which in turn is used during the generation of training datasets and when materializing feature values into the online store.

Project

Projects provide complete isolation of feature stores at the infrastructure level. This is accomplished through resource namespacing, e.g., prefixing table names with the associated project. Each project should be considered a completely separate universe of entities and features. It is not possible to retrieve features from multiple projects in a single request. We recommend having a single feature store and a single project per environment (dev, staging, prod).
Projects are currently being supported for backward compatibility reasons. Projects may change in the future as we simplify the Feast API.
Getting started - Previous
Concepts
Next
Data source
Last modified 20d ago
Export as PDF
Copy link
Contents
Project