OnlineStore
class.OnlineStoreConfig
class.OnlineStore
in a feature repo's feature_store.yaml
file.OnlineStore
class.update
and teardown
update
is invoked when users run feast apply
as a CLI command, or the FeatureStore.apply()
sdk method.update
method should be used to perform any operations necessary before data can be written to or read from the store. The update
method can be used to create MySQL tables in preparation for reads and writes to new feature views.teardown
is invoked when users run feast teardown
or FeatureStore.teardown()
.teardown
method should be used to perform any clean-up operations. teardown
can be used to drop MySQL indices and tables corresponding to the feature views being deleted.online_write_batch
and online_read
.online_write_batch
is invoked when running materialization (using the feast materialize
or feast materialize-incremental
commands, or the corresponding FeatureStore.materialize()
method.online_read
is invoked when reading values from the online store using the FeatureStore.get_online_features()
method.FeastConfigBaseModel
class, which is defined here.FeastConfigBaseModel
is a pydantic class, which parses yaml configuration into python objects. Pydantic also allows the model classes to define validators for the config classes, to make sure that the config classes are correctly defined.type
field, which contains the fully qualified class name of its corresponding OnlineStore class.Config
suffix.feature_store.yaml
as follows:config: RepoConfig
parameter which is passed into all the methods of the OnlineStore interface, specifically at the config.online_store
field of the config
parameter.feature_store.yaml
file, specifically in the online_store
field. The value specified should be the fully qualified class name of the OnlineStore.feature_store.yaml
:type
of the online store class as the value for the online_store
.OnlineStore
class in a separate repo, you can still test your implementation against the Feast test suite, as long as you have Feast as a submodule in your repo. In the Feast submodule, we can run all the unit tests with:FULL_REPO_CONFIGS
variable defined in sdk/python/tests/integration/feature_repos/repo_configuration.py
. To overwrite these configurations, you can simply create your own file that contains a FULL_REPO_CONFIGS
, and point Feast to that file by setting the environment variable FULL_REPO_CONFIGS_MODULE
to point to that file. In this repo, the file that overwrites FULL_REPO_CONFIGS
is feast_custom_online_store/feast_tests.py
, so you would run