fix(storage): correct QueryVectorsResponse to use vectors instead of matches #1922
+31
−29
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
mandarini
force-pushed
the
fix/wrong-type-vector
branch
from
509317a to
f32b2d4
Compare
o-santi
approved these changes
Dec 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
QueryVectorsResponseinterface to usevectorsfield instead ofmatchesto align with the actual AWS S3 Vectors APIdistanceMetricfield to the response typeContext
The TypeScript interface for
QueryVectorsResponseincorrectly defined the response field asmatches, but the actual AWS S3 Vectors API returnsvectors. This caused a mismatch between the SDK types and real API responses.References: