Hey all! I'm running into an issue with special characters contained within the

queries

option of the

vector_query

search parameter. The only reference I've found in the docs related to special character handling is specific to

filter_by

(here). Trying this approach and other common special character escaping strategies results in the same error when

query_weights

is included. Example: query with weights

{
   ...,
   "vector_query": "embeddedField:([], queries:[Butanediol, 1,4-Butanediol, BDO], query_weights:[0.4, 0.2, 0.2], alpha:0.75)",
}

Results

RequestMalformed: Request failed with HTTP code 400 | Server said: Malformed vector query string: queries and query_weights must be of the same length.

It's important to note that removing the weights and any escaping techniques does produce results, however, it is silently splitting our array of 3 terms (

Butanediol

.

1,4-Butanediol

,

BDO

) into 4 (

Butanediol

.

1

,

4-Butanediol

,

BDO

).

This almost sounds like a parsing bug within vector_query. Could you help reproduce this using a minimal set of curl commands like this and then copy paste that into a GitHub issue?

@Jason Bosco I would agree. A hidden parsing bug that is only revealed when

query_weights

are included. I've added an issue here

Thank you for catching that and opening the issue

Yes, it looks to still be present in the v28.0.rc36