ESQL - fix dense_vector reading for null values #131808
Merged
Conversation
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
…vector-fix-null-values-reading
carlosdelest
added
>non-issue
Team:Analytics
elasticsearchmachine
removed
the
Team:Search Relevance
|
Pinging @elastic/es-analytical-engine (Team:Analytics) |
carlosdelest
requested review from
ChrisHegarty,
ioanatia,
svilen-mihaylov-elastic and
tteofili
tteofili
approved these changes
Jul 24, 2025
ioanatia
approved these changes
Jul 24, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Reading dense_vector values did not work well with nulls. This PR fixes that and adds tests to ensure null values are read correctly.