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

知识库召回测试报错 #20063

New Issue
Closed
opened 2026-02-21 20:05:41 -05:00 by yindo · 4 comments
yindo commented 2026-02-21 20:05:41 -05:00
Owner
Copy Link
Copy Source

Originally created by @freetom2999 on GitHub (Oct 31, 2025).

Self Checks

  • I have read the Contributing Guide and Language Policy.
  • This is only for bug report, if you would like to ask a question, please head to Discussions.
  • I have searched for existing issues search for existing issues, including closed ones.
  • I confirm that I am using English to submit this report, otherwise it will be closed.
  • 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

1.9.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

版本从1.3.1升级至1.9.2后历史知识库召回测试报错：
Query call with protocol GRPC search failed with message extract target vectors: class Vector_index_970a7384_4c88_45b6_8d22_96f654d5d272_Node does not have named vector default configured. Available named vectors map[].

Image

✔️ Expected Behavior

解决报错

❌ Actual Behavior

No response

Originally created by @freetom2999 on GitHub (Oct 31, 2025). ### Self Checks - [x] I have read the [Contributing Guide](https://github.com/langgenius/dify/blob/main/CONTRIBUTING.md) and [Language Policy](https://github.com/langgenius/dify/issues/1542). - [x] This is only for bug report, if you would like to ask a question, please head to [Discussions](https://github.com/langgenius/dify/discussions/categories/general). - [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 submit this report, otherwise it will be closed. - [x] 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：） - [x] Please do not modify this template :) and fill in all the required fields. ### Dify version 1.9.2 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce 版本从1.3.1升级至1.9.2后历史知识库召回测试报错： Query call with protocol GRPC search failed with message extract target vectors: class Vector_index_970a7384_4c88_45b6_8d22_96f654d5d272_Node does not have named vector default configured. Available named vectors map[]. <img width="1155" height="429" alt="Image" src="https://github.com/user-attachments/assets/257a72fc-e173-407a-afa8-6e5c114cbc4d" /> ### ✔️ Expected Behavior 解决报错 ### ❌ Actual Behavior _No response_
yindo added the 👻 feat:rag label 2026-02-21 20:05:41 -05:00
yindo closed this issue 2026-02-21 20:05:41 -05:00
yindo commented 2026-02-21 20:05:41 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Oct 31, 2025):

Hi @freetom2999! I'm Dosu and I’m helping the dify team.

This error happens because Dify 1.9.2 (and newer vector backends like Weaviate ≥4.0.0, Qdrant, TiDB-on-Qdrant) now require a named vector configuration called "default" in your vector database collection. Legacy collections created before the upgrade are missing this, so recall/search fails [source].

To fix it, you need to re-index or re-upload the affected knowledge/documents so the collections are recreated with the correct named vector configuration. There is currently no automated migration script; manual re-indexing is required. For large legacy knowledge bases, scripting the re-upload or exporting and re-importing data is recommended to trigger re-indexing with the new schema. If you use custom ingestion scripts, make sure they set the vector payload as {"default": embedding} [source].

A temporary workaround is to change the embedding model of the knowledge base, which triggers automatic re-indexing and resolves the error, but this may have limitations (such as requiring multiple embedding models and downtime during reindexing). If you need immediate access and cannot re-index right now, you may temporarily downgrade to Dify 1.9.1 until migration is done [source].

If you are using Weaviate, check out the migration guide for more details. For Qdrant or TiDB-on-Qdrant, the same principle applies: collections must be rebuilt to include the named vector.

If your dataset is large and manual re-upload is not practical, consider scripting the export/import or re-indexing process. If you let me know which vector backend you use, I can provide more tailored steps.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Chat with Dosu Join Discord Share on X

@dosubot[bot] commented on GitHub (Oct 31, 2025): <!-- Greeting --> Hi @freetom2999! I'm [Dosu](https://go.dosu.dev/dosubot) and I’m helping the dify team. <!-- Answer --> This error happens because Dify 1.9.2 (and newer vector backends like Weaviate ≥4.0.0, Qdrant, TiDB-on-Qdrant) now require a named vector configuration called `"default"` in your vector database collection. Legacy collections created before the upgrade are missing this, so recall/search fails [[source](https://github.com/langgenius/dify/issues/27432)]. To fix it, you need to re-index or re-upload the affected knowledge/documents so the collections are recreated with the correct named vector configuration. There is currently no automated migration script; manual re-indexing is required. For large legacy knowledge bases, scripting the re-upload or exporting and re-importing data is recommended to trigger re-indexing with the new schema. If you use custom ingestion scripts, make sure they set the vector payload as `{"default": embedding}` [[source](https://github.com/langgenius/dify/issues/27362)]. A temporary workaround is to change the embedding model of the knowledge base, which triggers automatic re-indexing and resolves the error, but this may have limitations (such as requiring multiple embedding models and downtime during reindexing). If you need immediate access and cannot re-index right now, you may temporarily downgrade to Dify 1.9.1 until migration is done [[source](https://github.com/langgenius/dify/issues/27432)]. If you are using Weaviate, check out the [migration guide](https://github.com/langgenius/dify/blob/main/docs/weaviate/WEAVIATE_MIGRATION_GUIDE/README.md) for more details. For Qdrant or TiDB-on-Qdrant, the same principle applies: collections must be rebuilt to include the named vector. If your dataset is large and manual re-upload is not practical, consider scripting the export/import or re-indexing process. If you let me know which vector backend you use, I can provide more tailored steps. <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/11bced33-d559-4ae3-903f-4997df71ceda?feedback_type=other)</sup>&nbsp;&nbsp;[![Chat with Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/6088a4f4-073a-43f3-b3d4-4f06fb0c05a0/ask?utm_source=github)&nbsp;[![Join Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share on X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/langgenius/dify/issues/27695)
yindo commented 2026-02-21 20:05:42 -05:00
Author
Owner
Copy Link
Copy Source

@freetom2999 commented on GitHub (Oct 31, 2025):

重新索引后解决。

@freetom2999 commented on GitHub (Oct 31, 2025): 重新索引后解决。
yindo commented 2026-02-21 20:05:42 -05:00
Author
Owner
Copy Link
Copy Source

@fangoner commented on GitHub (Nov 2, 2025):

重新索引后解决。

But it does not work for me by re-indexing, sigh.

@fangoner commented on GitHub (Nov 2, 2025): > 重新索引后解决。 But it does not work for me by re-indexing, sigh.
yindo commented 2026-02-21 20:05:42 -05:00
Author
Owner
Copy Link
Copy Source

@loujunhui commented on GitHub (Dec 4, 2025):

use dify version 1.10.1,rebuild index canot resolve it,always tip error info

@loujunhui commented on GitHub (Dec 4, 2025): use dify version 1.10.1,rebuild index canot resolve it,always tip error info
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 👻 feat:rag
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#20063
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?