Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test/fix requests with knn #2681

Closed
wants to merge 3 commits into from
Closed

Conversation

PavelShilin89
Copy link
Contributor

Type of Change (select one):

  • Bug fix

Description of the Change:
A test has been created confirming that:

  • The issue with handling a string array when inserting into a float_vector field has been fixed. The system now correctly reports the need to use a numeric array.
  • The error message for executing a KNN query on a table with an incorrect structure has been corrected. The system now returns an accurate message indicating the absence of index parameters for the float_vector field.
  • The issue with executing KNN queries without explicitly specifying index parameters has been fixed. Previously, when creating a table with a float_vector field without parameters such as knn_type, knn_dims, and hnsw_similarity, KNN queries would return the error “Undefined array key 0”. Now, the system provides a proper message indicating that the indexing parameters must be defined.
  • The issue with handling KNN queries when using an int field as the vector field has been addressed. Now, when attempting to execute a KNN query with an int field, the system correctly returns an error indicating the data type mismatch, instead of a message about incorrect return type in the getQueryVectorValue() function.

Related Issue (provide the link):

@PavelShilin89
Copy link
Contributor Author

Закрыт, выполнено в другом PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants