You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@woop what do you mean by doesn't exist? I see data_source_class_type in DataSource.proto:
// This is an internal field that is represents the python class for the data source object a proto object represents.
// This should be set by feast, and not by users.
string data_source_class_type = 17;
and I also see it being set correctly in the code:
Yep. I think there is some bug that might have been introduced when we started storing data sources separately since the feature view class adds that, but i don't think we add this class_type with applying data sources to the registry.
For some reason we are using field names
feast/sdk/python/feast/data_source.py
Line 217 in b35e1e8
Also,
feast/sdk/python/feast/data_source.py
Line 213 in b35e1e8
The text was updated successfully, but these errors were encountered: