fix(milvus): use explicit output_fields in query_vector for milvus-lite 3.0 compatibility#6091
Merged
Conversation
…te 3.0 compatibility milvus-lite 3.0 no longer expands output_fields=["*"] to include JSON fields in client.search() results, causing KeyError: 'chunk_content'. Use explicit field name, consistent with query_keyword and query_hybrid. Closes: ogx-ai#6090 Co-Authored-By: Claude Opus 4.6 <[email protected]> Signed-off-by: Derek Higgins <[email protected]>
derekhiggins
requested review from
bbrowning,
cdoern,
franciscojavierarceo,
leseb,
mattf,
raghotham and
skamenan7
as code owners
June 12, 2026 08:32
cdoern
approved these changes
Jun 12, 2026
Collaborator
|
@Mergifyio backport release-1.1.x |
Contributor
✅ Backports have been createdDetails
|
4 tasks
cdoern
pushed a commit
that referenced
this pull request
Jun 12, 2026
…te 3.0 compatibility (backport #6091) (#6096) ## Summary - `query_vector` used `output_fields=["*"]` in `client.search()`, but milvus-lite 3.0 no longer expands `["*"]` to include JSON fields in search results, causing `KeyError: 'chunk_content'` - Changed to `output_fields=["chunk_content"]`, consistent with `query_keyword` and `query_hybrid` which already use explicit field names - The `remote::milvus` provider (connecting to a full Milvus server) was not affected Closes #6090 RHAIENG-5601 ## Test plan - [x] Reproduced the bug with milvus-lite 3.0 via standalone script - [x] Reproduced via REST API (`/v1/vector-io/query` returns 500, `/v1/vector_stores/{id}/search` returns empty) - [x] Verified fix works with milvus-lite 3.0 - both endpoints return correct results - [x] Fix is backward compatible with milvus-lite 2.x (explicit field names work in both versions)<hr>This is an automatic backport of pull request #6091 done by [Mergify](https://mergify.com). Signed-off-by: Derek Higgins <[email protected]> Co-authored-by: Derek Higgins <[email protected]> Co-authored-by: Claude Opus 4.6 <[email protected]>
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.
Summary
query_vectorusedoutput_fields=["*"]inclient.search(), but milvus-lite 3.0 no longer expands["*"]to include JSON fields in search results, causingKeyError: 'chunk_content'output_fields=["chunk_content"], consistent withquery_keywordandquery_hybridwhich already use explicit field namesremote::milvusprovider (connecting to a full Milvus server) was not affectedCloses #6090
RHAIENG-5601
Test plan
/v1/vector-io/queryreturns 500,/v1/vector_stores/{id}/searchreturns empty)