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]: Prepare.search_requests_with_expr() got multiple values for argument 'expr' #34118

Closed
1 task done
iamsaurabhgupt opened this issue Jun 24, 2024 · 1 comment
Closed
1 task done
Assignees
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@iamsaurabhgupt
Copy link

iamsaurabhgupt commented Jun 24, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Environment

- Milvus version:2.4.1
- Deployment mode(standalone or cluster): cluster
- MQ type(rocksmq, pulsar or kafka)
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus[model]==2.4.4
- OS(Ubuntu or CentOS): Ubuntu
- CPU/Memory: 75/600Gi
- GPU: 2
- Others:

Current Behavior

search_args = {'limit': 9, 'output_fields': ['_id', 'content'], 'expr': 'param == abc'}
collection.hybrid_search([sparse_request, dense_request], rerank=rerank, **search_args)

This is giving error
raise MilvusException(message=f"Unexpected error, message=<{e!s}>") from e
pymilvus.exceptions.MilvusException: <MilvusException: (code=1, message=Unexpected error, message=<Prepare.search_requests_with_expr() got multiple values for argument 'expr'>)>

Expected Behavior

No response

Steps To Reproduce

No response

Milvus Log

No response

Anything else?

No response

@iamsaurabhgupt iamsaurabhgupt 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 Jun 24, 2024
@iamsaurabhgupt
Copy link
Author

Figured out. It was our mistake. The expr was supposed to be inside sparse_request and dense_request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Issues or changes related a bug needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants