langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-21 20:15:31 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Qdrant as vector store does not work #907

New Issue
Closed
opened 2026-02-21 17:28:58 -05:00 by yindo · 8 comments
yindo commented 2026-02-21 17:28:58 -05:00
Owner
Copy Link
Copy Source

Originally created by @wpt1225 on GitHub (Jan 15, 2024).

Originally assigned to: @takatost, @JohnJyong on GitHub.

Self Checks

Provide a description of the help you need

I am using version 0.4.6 of dify and merged dify qdrant code. local deployment, not docker.
Qdrant version 1.7.3(local deployment, not Docker)
When I create a knowledge base and select "high quality" indexing，The following exception occurred：

qdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 400 (Bad Request)
Raw response content:
b'{"status":{"error":"Deserialize error in query parameters: invalid digit found in string"},"time":0.0}'

May I ask if there is a solution

Originally created by @wpt1225 on GitHub (Jan 15, 2024). Originally assigned to: @takatost, @JohnJyong on GitHub. ### Self Checks - [X] I have searched for existing issues [search for existing issues](https://github.com/langgenius/dify/issues), including closed ones. - [X] I confirm that I am using English to file this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). ### Provide a description of the help you need I am using version 0.4.6 of dify and merged dify qdrant code. local deployment, not docker. Qdrant version 1.7.3(local deployment, not Docker) When I create a knowledge base and select "high quality" indexing，The following exception occurred： qdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 400 (Bad Request) Raw response content: b'{"status":{"error":"Deserialize error in query parameters: invalid digit found in string"},"time":0.0}' May I ask if there is a solution
yindo added the 🐞 bug label 2026-02-21 17:28:58 -05:00
yindo closed this issue 2026-02-21 17:28:58 -05:00
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Jan 15, 2024):

🤖

Hey there @wpt1225! 👋 I'm Dosu, your friendly neighborhood bot. I'm here to lend a hand with those pesky bugs, answer your burning questions, and guide you on your journey to becoming a contributor. While we're waiting for human maintainers to join the conversation, feel free to ask me anything. I'm here to help! 🤖 🤓

Based on the error message you provided, it seems like there's an issue with the data types of the query parameters or payload when the "high quality" indexing option is selected in Qdrant version 1.7.3. This error typically occurs when a string value is being incorrectly parsed as a number.

Unfortunately, without specific code or configuration related to the "high quality" indexing in Qdrant version 1.7.3, it's hard to provide a specific solution. I recommend checking the data types for all parameters and payload according to the Qdrant and dify documentation.

If the issue persists, you may need to debug the specific query or operation that is causing this error to identify the root cause. You can refer to the qdrant.py file in the dify repository for more details on how Qdrant is integrated with dify.

Also, I found a similar issue in the dify repository: 向量数据库选qdrant，创建知识库时异常. Although it's not exactly the same, it might provide some insights into your problem.

If you could provide more details about the specific query parameters being passed when the "high quality" indexing option is selected, it would be easier to identify the root cause of the problem.

Sources

This response is meant to be useful and save you time. It is not meant to be a precise solution, but rather a starting point for your own research.

Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant.

If you want to continue the conversation, start your reply with @dosu-bot.

@dosubot[bot] commented on GitHub (Jan 15, 2024): _🤖_ <!-- Greeting --> Hey there @wpt1225! :wave: I'm [Dosu](https://dosu.dev), your friendly neighborhood bot. I'm here to lend a hand with those pesky bugs, answer your burning questions, and guide you on your journey to becoming a contributor. While we're waiting for human maintainers to join the conversation, feel free to ask me anything. I'm here to help! :robot: :nerd_face: <!-- Answer --> Based on the error message you provided, it seems like there's an issue with the data types of the query parameters or payload when the "high quality" indexing option is selected in Qdrant version 1.7.3. This error typically occurs when a string value is being incorrectly parsed as a number. Unfortunately, without specific code or configuration related to the "high quality" indexing in Qdrant version 1.7.3, it's hard to provide a specific solution. I recommend checking the data types for all parameters and payload according to the Qdrant and dify documentation. If the issue persists, you may need to debug the specific query or operation that is causing this error to identify the root cause. You can refer to the [qdrant.py](https://github.com/langgenius/dify/blob/main/api/core/vector_store/vector/qdrant.py) file in the dify repository for more details on how Qdrant is integrated with dify. Also, I found a similar issue in the dify repository: [向量数据库选qdrant，创建知识库时异常](https://github.com/langgenius/dify/issues/2028). Although it's not exactly the same, it might provide some insights into your problem. If you could provide more details about the specific query parameters being passed when the "high quality" indexing option is selected, it would be easier to identify the root cause of the problem. ## Sources - [向量数据库选qdrant，创建知识库时异常](https://github.com/langgenius/dify/issues/2028) - [api/core/vector_store/vector/qdrant.py](https://github.com/langgenius/dify/blob/main/api/core/vector_store/vector/qdrant.py) --- This response is meant to be useful and save you time. It is **not meant to be a precise solution**, but rather a starting point for your own research. Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is irrelevant. If you want to continue the conversation, start your reply with @dosu-bot.
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Jan 15, 2024):

We use https://github.com/langgenius/dify/blob/1fe4e3afde262e51621d4b388dd28c5e8fd91354/api/requirements.txt#L56 this version of qdrant in dify.
Seems we do not support the latest version of qdrant. Ca you try to downgrade the version to see if this is helpful.
We will upgrade this client in the future. @takatost

@crazywoola commented on GitHub (Jan 15, 2024): We use https://github.com/langgenius/dify/blob/1fe4e3afde262e51621d4b388dd28c5e8fd91354/api/requirements.txt#L56 this version of qdrant in dify. Seems we do not support the latest version of qdrant. Ca you try to downgrade the version to see if this is helpful. We will upgrade this client in the future. @takatost
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@takatost commented on GitHub (Jan 15, 2024):

We use

https://github.com/langgenius/dify/blob/1fe4e3afde262e51621d4b388dd28c5e8fd91354/api/requirements.txt#L56

this version of qdrant in dify.
Seems we do not support the latest version of qdrant. Ca you try to downgrade the version to see if this is helpful.
We will upgrade this client in the future. @takatost

@JohnJyong pls check it out.

@takatost commented on GitHub (Jan 15, 2024): > We use > > https://github.com/langgenius/dify/blob/1fe4e3afde262e51621d4b388dd28c5e8fd91354/api/requirements.txt#L56 > > this version of qdrant in dify. > Seems we do not support the latest version of qdrant. Ca you try to downgrade the version to see if this is helpful. > We will upgrade this client in the future. @takatost @JohnJyong pls check it out.
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@JohnJyong commented on GitHub (Jan 15, 2024):

pls attach your qdrant setting in your env

@JohnJyong commented on GitHub (Jan 15, 2024): pls attach your qdrant setting in your env
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@wpt1225 commented on GitHub (Jan 15, 2024):

I have downgrade the qdrant version to 1.6.1 and it works well

@wpt1225 commented on GitHub (Jan 15, 2024): I have downgrade the qdrant version to 1.6.1 and it works well
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@takatost commented on GitHub (Jan 15, 2024):

I have downgrade the qdrant version to 1.6.1 and it works well

So you mean qdrant-client==1.6.4 is not compatible with qdrant server (v1.7.3), and qdrant server can be downgraded to 1.6.1 and works well, right?
@JohnJyong pls check it out.

@takatost commented on GitHub (Jan 15, 2024): > I have downgrade the qdrant version to 1.6.1 and it works well So you mean qdrant-client==1.6.4 is not compatible with qdrant server (v1.7.3), and qdrant server can be downgraded to 1.6.1 and works well, right? @JohnJyong pls check it out.
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@wpt1225 commented on GitHub (Jan 15, 2024):

I have downgrade the qdrant version to 1.6.1 and it works well

So you mean qdrant-client==1.6.4 is not compatible with qdrant server (v1.7.3), and qdrant server can be downgraded to 1.6.1 and works well, right? @JohnJyong pls check it out.

Yes, when I use the qdrant server (v1.7.3), the request error code is 400
qdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 400 (Bad Request)

@wpt1225 commented on GitHub (Jan 15, 2024): > > I have downgrade the qdrant version to 1.6.1 and it works well > > So you mean qdrant-client==1.6.4 is not compatible with qdrant server (v1.7.3), and qdrant server can be downgraded to 1.6.1 and works well, right? @JohnJyong pls check it out. Yes, when I use the qdrant server (v1.7.3), the request error code is 400 qdrant_client.http.exceptions.UnexpectedResponse: Unexpected Response: 400 (Bad Request)
yindo commented 2026-02-21 17:28:59 -05:00
Author
Owner
Copy Link
Copy Source

@JohnJyong commented on GitHub (Jan 16, 2024):

it has fixed , pls fetch the latest code~
thanks for your feedback @wpt1225

@JohnJyong commented on GitHub (Jan 16, 2024): it has fixed , pls fetch the latest code~ thanks for your feedback @wpt1225
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Knowledge Pipeline
Proposal
WIP
cloud
dependencies
feat:webapp
good first issue
outdated
performance
pull-request
Mirrored from GitHub Pull Request
 python:uv
refactor
size:L
stale
status: accepting prs
status: blocked
status: in discussion
stt & tts
vulnerablity
web
wont-fix
🌊 feat:workflow
🌚 invalid
🐞 bug
👻 feat:rag
💪 enhancement
📚 documentation
🔨 feat:tools
🙋‍♂️ question
🙏 help wanted
🤔 cant-reproduce
🤖 feat:agent
No Label 🐞 bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#907
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?