-
Notifications
You must be signed in to change notification settings - Fork 999
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SQL Registry does not populate cache correctly #3430
Comments
Confirmed issue still exists in 0.28.0 |
Confirmed issue still exists in 0.29.0 |
We have the same issue and my debugging leads to the same solution as mentioned above. |
Incase it's helpful for anyone, I've been using the following fix in my project for a couple of versions now (works in at least 0.27.1 through 0.29.0). Replace this line with the following:
I can't guarantee it's totally correct, but I haven't had any problems with it thus far. |
Thanks for the fix. Looking forward for the new release. Is there any timeline for the new release? |
Expected Behavior
Using SQL registry, should be able to retrieve online features for an existing feature view using the Python SDK.
Current Behavior
FeatureStore.get_online_features() currently returns a FeatureviewNotFoundException, despite the feature view existing as evidenced by the output of FeatureStore.list_feature_views().
Steps to reproduce
Specifications
Possible Solution
This error seems to be specific to the SQL registry, as I have followed the exact same steps using a File registry and there is no issue. I can also circumvent the error by disabling the cache for the SQL registry, so it seems localized to the SQL registry cache itself. The feature views are successfully retrieved, but are rejected by this line because their spec does not have a project.
It appears that normally, the project is attached to the proto spec right before committing registry changes (like so, but the SQL registry does not do this and instead relies on each class's to_proto() output, which does not contain the project. This issue appears to extend to other types of objects as well (entities, etc.)
The text was updated successfully, but these errors were encountered: