fix: Updated the elastic search to use vector_index defined in the feature view to identify vector fields#348
Merged
vanitabhagwat merged 3 commits intofeature/vector-storefrom Mar 31, 2026
Conversation
… view to identify vector fields
vanitabhagwat
changed the title
piket
reviewed
Mar 30, 2026
Comment on lines
+517
to
+519
| if is_vector: | ||
| vector_val = get_list_val_str(value) | ||
| if vector_val: |
Collaborator
There was a problem hiding this comment.
Should we add a log in the case that the vector_val is empty?
piket
approved these changes
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updated the elastic search to use vector_index defined in the feature view to identify vector fields.
What this PR does / why we need it:
Which issue(s) this PR fixes:
Misc