Expected Behavior
When FeatureViews have online=False, running feast ui should start the UI and load the project.
Current Behavior
The UI fails to load with the following error:
Error Loading Project Configs
There was an error loading the Project Configurations. Please check that feature_store.yaml file is available and well-formed.
This looks like it is caused by the registry dump not containing the online key for the feature views.
Steps to reproduce
- Create a default repo using
feast init
- In
example.py change online=True to online=False.
- Run
feast ui
Specifications
- Version: 0.21.2
- Platform: macOS
- Subsystem:
Possible Solution
To fix this, the registry should always contain the online key for FeatureViews even if they are set to False.
Perhaps this is related to this quirk of protobufs: protocolbuffers/protobuf#1772 which would mean that the online key doesn't come through in the call to to_proto here:
|
self._message_to_sorted_dict(feature_view.to_proto()) |
Expected Behavior
When FeatureViews have
online=False, runningfeast uishould start the UI and load the project.Current Behavior
The UI fails to load with the following error:
This looks like it is caused by the registry dump not containing the
onlinekey for the feature views.Steps to reproduce
feast initexample.pychangeonline=Truetoonline=False.feast uiSpecifications
Possible Solution
To fix this, the registry should always contain the
onlinekey for FeatureViews even if they are set to False.Perhaps this is related to this quirk of protobufs: protocolbuffers/protobuf#1772 which would mean that the
onlinekey doesn't come through in the call toto_protohere:feast/sdk/python/feast/registry.py
Line 914 in f4eed30