Compatibility issue between v0.21.x and v0.28.x

[gbmarc1]

The new entity_columns attribute was added to the FeitureView class after 0.21. When a newer version of Feast reads the 0.21.x registry, it does not populate the entity_columns attribute leading to downstream inconsistencies.

One such inconsistencies occurs when getting historical features from the BigQuery offline store. There are no entities and the resulting query does not behave properly.

Expected Behavior

It would be nice if we could read the 0.21.x registry from the 0.28.x version. The other way around could prove to be useful when migrating an organization from Feast 0.21 -> 0.28. We may update the registry to 0.28 but some jobs will still have a 0.21 dependency. I did not test the later but will do shortly and update the issue.

edit: It is possible to read the 0.28 registry with 0.21 code. 0.21 python sdk seems to work appropriately which is good news for migration.

Current Behavior

Reading the 0.21.x registry from the 0.28.x registry leads to unexpected behaviours that is due to an empty entity_columns attribute.

Steps to reproduce

• Install 0.21.x
• Apply the registry
• Install 0.28.x
• List all feature views -> entity_columns should be empty

Specifications

• Version: 0.28.1 (Feast) - 0.21.1 (registry)
• Platform:
• Subsystem:

Possible Solution

TBD

[stale]

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.