Search…
v0.25-branch
Introduction
Community & getting help
Roadmap
Changelog
Getting started
Quickstart
Concepts
Architecture
Third party integrations
FAQ
Tutorials
Sample use-case tutorials
Validating historical features with Great Expectations
Using Scalable Registry
Building streaming features
How-to Guides
Running Feast with Snowflake/GCP/AWS
Running Feast in production (e.g. on Kubernetes)
Upgrading for Feast 0.20+
Customizing Feast
Adding or reusing tests
Reference
Codebase Structure
Type System
Data sources
Offline stores
Online stores
Providers
Local
Google Cloud Platform
Amazon Web Services
Azure
Batch Materialization Engines
Feature repository
Feature servers
[Beta] Web UI
[Alpha] On demand feature view
[Alpha] Data quality monitoring
Feast CLI reference
Python API reference
Usage
Project
Contribution process
Development guide
Backwards Compatibility Policy
Versioning policy
Release process
Feast 0.9 vs Feast 0.10+
Powered By GitBook
Amazon Web Services

Description

  • Offline Store: Uses the Redshift offline store by default. Also supports File as the offline store.
  • Online Store: Uses the DynamoDB online store by default. Also supports Sqlite as an online store.

Getting started

In order to use this offline store, you'll need to run (Snowflake) pip install 'feast[aws, snowflake]' or (Redshift) pip install 'feast[aws]'.
You can get started by then running feast init -t snowflake or feast init -t aws.

Example

feature_store.yaml
project: my_feature_repo
registry: data/registry.db
provider: aws
online_store:
type: dynamodb
region: us-west-2
offline_store:
type: redshift
region: us-west-2
cluster_id: feast-cluster
database: feast-database
user: redshift-user
s3_staging_location: s3://feast-bucket/redshift
iam_role: arn:aws:iam::123456789012:role/redshift_s3_access_role
Previous
Google Cloud Platform
Next
Azure
Last modified 11h ago
Export as PDF
Copy link
Edit on GitHub
On this page
Description
Getting started
Example