Fix a bug: incorrect outputFields of query/search with milvus v2.5.8 #1355
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.
In milvus v2.5.8, the returned QueryResults is changed, the output_fields member doesn't contain the primary key name.
in milvus versions <= v2.5.7, the QueryResults.output_fields always contains the primary key name. And Java SDK uses the QueryResults.output_fields to fetch data.
So, with milvus v2.5.8, the Java SDK query() cannot get the primary key values. This pr is to follow the logic of pymilvus. In pymilvus, the QueryResults.output_fields is ignored.