Open xiaojunxiang2023 opened 1 day ago
@xiaojunxiang2023 you are using 2.4.x but from my knowlege milvus 2.4 don't have rust related logic. Only 2.5 when we introduce tantivy. can you share your test code if possible? Are you using prefix filtering, A like "AA%" or random like "%AA%"
/assign @sunby please help on it as well
It looks like the query expression is "^%" and it is parsed to "^(.|\n)*" which is invalid for regex parser. We should escape the origin pattern and then pass it to tantivy.
Is there an existing issue for this?
Environment
Current Behavior
When my client uses a scalar field as the query condition, it causes the querynode to crash. The querynode logs show an error indicating the presence of illegal characters.
The content of my scalar field is:
ABC!DEFGHI-JK_@#$%^&*LMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789
I think Milvus:
Expected Behavior
I think this logic is very unreasonable. Validation should be done during data insertion or at the time of building the index, and any issues should be raised then, rather than waiting until the data is actually used to throw an error.
Steps To Reproduce
Milvus Log
No response
Anything else?
No response