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.
Type of Change (select one):
Description of the Change: A test has been created confirming that:
Related Issue (provide the link):