Open TaherehFarrokhi opened 2 years ago
Any news on this one?
Seems to me this is an implementation decision and not a bug (whether introduced or not), then this could be a feature request... The old version ran a SELECT INTO
from sql string in the entity table
I encountered a similar issue where the insertion operation defaults the string column in an entity table with varchar(1) which violates the length check.
I believe this might have been just an incorrect gate. The other offline stores allow for this and it seemed to work in the old version. We should be able to re-enable this and fix any tests that are failing as a result
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Expected Behavior
In Feast version 0.18.1, it was poosible to get historical features by passing a sql query as entity_df and it returns the values
Current Behavior
When I updated or .24+ it returns error :
string entities are currently not supported in the MsSQL offline store.
https://github.com/feast-dev/feast/blob/master/sdk/python/feast/infra/offline_stores/contrib/mssql_offline_store/mssql.py#L189
Steps to reproduce
this is my feast_store.yaml
Specifications
Possible Solution