-
-
Notifications
You must be signed in to change notification settings - Fork 18.9k
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]Issue with Qdrant Collection Configuration Filter in JSON Payload #910
Comments
Hey @samsam002. Could you provide your flow-setup? |
thanks for the reactivity, i'm wondering if the args qdrantCollectionCofiguration is even meant for filtering ? |
I seem to have found the issue here. You're trying to filter the results by passing the filter obj to the |
thanks for the feedback, any clue to get filtered result as in the "pinecone load existing " one ? |
As of now, the filters params aren't configurable when querying with Flowise and Qdrant. I'll see to parameterize this value. |
This comment was marked as off-topic.
This comment was marked as off-topic.
I'm working on adding the filter. Should be done by today if everything goes right. I'll let you know when the PR is up. |
@samsam002, you can checkout #912. {
"question":"Your question",
"overrideConfig":{
"qdrantFilter":{
"must":[
{
"key":"classuers",
"match":{
"any":[
"black",
"yellow"
]
}
}
]
}
}
} Should be usable now. |
GREAT thanks to you. i'll test it out and feed back. |
Description:
I am trying to send a JSON payload with a specific filter configuration according to the Flowise documentation. However, I am encountering issues with the filter not working as expected.
JSON Payload:
Expected Outcome:
I expected the filter to work correctly, filtering the results based on the classuers field matching any of the specified values ("black", "yellow").
But it never filters the output.
Here is the strucutre of points in Qdrant

The text was updated successfully, but these errors were encountered: