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

[Bug]: If the text in Text Match contains a \n (line break) symbol, the query plan will parse incorrectly. #37367

Open
1 task done
zhuwenxing opened this issue Nov 1, 2024 · 0 comments
Assignees
Labels
2.5-features feature/text match kind/bug Issues or changes related a bug severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Milestone

Comments

@zhuwenxing
Copy link
Contributor

zhuwenxing commented Nov 1, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:master-20241031-4bac2eb1-amd64
- Deployment mode(standalone or cluster):
- MQ type(rocksmq, pulsar or kafka):    
- SDK version(e.g. pymilvus v2.0.0rc2):
- OS(Ubuntu or CentOS): 
- CPU/Memory: 
- GPU: 
- Others:

Current Behavior

If the text matched by text match is generated through query_data = faker.text(max_nb_chars=300), an error will be reported.

[2024-11-01 16:10:18,178] wxzhu-macbook-pro/ERROR/milvus_locust: Query error: <MilvusException: (code=1100, message=failed to create query plan: cannot parse expression: TextMatch(text, 'Voice report mission onto they old realize. Happen institution capital goal team two wonder.
Red million fund little. Line strategy fund however. Between available of father.'), error: line 2:80 token recognition error at: '.'': invalid parameter)>

image

If the text matched by text match is generated through query_data = faker.text(max_nb_chars=300).replace("\n", " "), it works well.

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@zhuwenxing zhuwenxing added kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 1, 2024
@zhuwenxing zhuwenxing added this to the 2.5.0 milestone Nov 1, 2024
@zhuwenxing zhuwenxing assigned aoiasd and unassigned yanliang567 Nov 1, 2024
@yanliang567 yanliang567 added triage/accepted Indicates an issue or PR is ready to be actively worked on. 2.5-features and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Nov 1, 2024
@zhuwenxing zhuwenxing added the severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. label Nov 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.5-features feature/text match kind/bug Issues or changes related a bug severity/critical Critical, lead to crash, data missing, wrong result, function totally doesn't work. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants