[Alpha] Saved dataset
Feast datasets allow for conveniently saving dataframes that include both features and entities to be subsequently used for data analysis and model training. Data Quality Monitoring was the primary motivation for creating dataset concept.
Dataset's metadata is stored in the Feast registry and raw data (features, entities, additional input keys and timestamp) is stored in the offline store.
Dataset can be created from:
  1. 1.
    Results of historical retrieval
  2. 2.
    [planned] Logging request (including input for on demand transformation) and response during feature serving
  3. 3.
    [planned] Logging features during writing to online store (from batch source or stream)

Creating a saved dataset from historical retrieval

To create a saved dataset from historical features for later retrieval or analysis, a user needs to call get_historical_features method first and then pass the returned retrieval job to create_saved_dataset method. create_saved_dataset will trigger the provided retrieval job (by calling .persist() on it) to store the data using the specified storage behind the scenes. Storage type must be the same as the globally configured offline store (e.g it's impossible to persist data to a different offline source). create_saved_dataset will also create a SavedDataset object with all of the related metadata and will write this object to the registry.
from feast import FeatureStore
from feast.infra.offline_stores.bigquery_source import SavedDatasetBigQueryStorage
store = FeatureStore()
historical_job = store.get_historical_features(
dataset = store.create_saved_dataset(
tags={'author': 'oleksii'}
Saved dataset can be retrieved later using the get_saved_dataset method in the feature store:
dataset = store.get_saved_dataset('my_training_dataset')
Check out our tutorial on validating historical features to see how this concept can be applied in a real-world use case.
Export as PDF
Copy link
Edit on GitHub