Expected Behavior

Let's say I have two arrays in a store, the first one of size k and the other one of size m
In the current behavior of Feast, we define in the feature_store.yaml

online_store:
  ...
  vector_len: 64
  ...

Here k == 64 is the size of the embedding vector that will be used in the online store,
If I want to push to the store an array that isn't of size k == 64 I will get an error even if the array is defined as vector_index=False in the Feature View,

From my perspective, the vector_len parameter needs to be defined per field in a FeatureView, or even not predefined.

Current Behavior

When pushing to a store a vector of size m when m != k where in the feature_repo.yaml defined vector_len: k
an error rise
DataException: expected 64 dimensions, not 10

Steps to reproduce

Create feature view and push a vector of size that is different from the defined feature_repo.yaml file

Specifications

• Version: 0.46.0
• Platform: local
• Subsystem: Fedora

Possible Solution