OfflineStore
interface, along with the core functionality supported by the method:get_historical_features
: point-in-time correct join to retrieve historical featurespull_latest_from_table_or_query
: retrieve latest feature values for materialization into the online storepull_all_from_table_or_query
: retrieve a saved datasetoffline_write_batch
: persist dataframes to the offline store, primarily for push sourceswrite_logged_features
: persist logged features to the offline store, for feature loggingRetrievalJob
specific to an offline store, such as a SnowflakeRetrievalJob
. Here is a list of functionality supported by RetrievalJob
s:RetrievalJob
s are lazily executed)FileOfflineStore
, BigQueryOfflineStore
, SnowflakeOfflineStore
, and RedshiftOfflineStore
. There are several additional implementations contributed by the Feast community (PostgreSQLOfflineStore
, SparkOfflineStore
, and TrinoOfflineStore
), which are not guaranteed to be stable or to match the functionality of the core implementations. Details for each specific offline store, such as how to configure it in a feature_store.yaml
, can be found here.get_historical_features
pull_latest_from_table_or_query
pull_all_from_table_or_query
offline_write_batch
write_logged_features
RetrievalJob
s support what functionality.