Warning: This is an experimental feature. It's intended for early testing and feedback, and could change without warnings in future releases.
Push sources allow feature values to be pushed to the online store in real time. This allows fresh feature values to be made available to applications. Push sources supercede the FeatureStore.write_to_online_store.
Push sources can be used by multiple feature views. When data is pushed to a push source, Feast propagates the feature values to all the consuming feature views.
Push sources must have a batch source specified, since that's the source used when retrieving historical features. When using a PushSource as a stream source in the definition of a feature view, a batch source doesn't need to be specified in the definition explicitly.
Streaming data sources are important sources of feature values. A typical setup with streaming data looks like:
Raw events come in (stream 1)
Streaming transformations applied (e.g. generating features like last_N_purchased_categories
) (stream 2)
Write stream 2 values to an offline store as a historical log for training
Write stream 2 values to an online store for low latency feature serving
Periodically materialize feature values from the offline store into the online store for improved correctness
Feast now allows users to push features previously registered in a feature view to the online store for fresher features.
Note that the push schema needs to also include the entity
See also Python feature server for instructions on how to push data to a deployed feature server.