René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Eliminate vector length restrictions in the store","articleBody":"## Expected Behavior \nLet's say I have two arrays in a store, the first one of size `k` and the other one of size `m`\nIn the current behavior of Feast, we define in the feature_store.yaml\n\n```\nonline_store:\n  ...\n  vector_len: 64\n  ...\n```\nHere `k == 64` is the size of the embedding vector that will be used in the online store,\nIf 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,\n\nFrom my perspective, the `vector_len` parameter needs to be defined `per field` in a FeatureView, or even not predefined.\n\n## Current Behavior\nWhen pushing to a store a vector of size `m` when `m != k` where in the feature_repo.yaml defined  ` vector_len: k` \nan error rise\n`DataException: expected 64 dimensions, not 10`\n\n## Steps to reproduce\nCreate feature view and push a vector of size that is different from the defined feature_repo.yaml file\n\n### Specifications\n\n- Version: 0.46.0\n- Platform: local \n- Subsystem: Fedora\n\n## Possible Solution\n","author":{"url":"https://github.com/itay1551","@type":"Person","name":"itay1551"},"datePublished":"2025-03-20T09:45:33.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/5166/feast/issues/5166"}