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

"Knowledge" block settings: The implementation and the documentation are different. #7344

New Issue
Closed
opened 2026-02-21 18:20:05 -05:00 by yindo · 1 comment
yindo commented 2026-02-21 18:20:05 -05:00
Owner
Copy Link
Copy Source

Originally created by @tden-TakahitoUsui on GitHub (Dec 22, 2024).

Self Checks

  • 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 (我已阅读并同意 Language Policy).
  • [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
  • Please do not modify this template :) and fill in all the required fields.

Dify version

0.14.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

I set the "Knowledge" in Dify "0.14.1".

  • Index Method: Economical
  • Retrieval Setting: Inverted Index

✔️ Expected Behavior

I hope when the workflow use one "Knowledge", the rerank model is optional.

❌ Actual Behavior

When I use "Knowledge Retrieval" block with this "Knowledge", Dify says "Rerank Model is required". But in this setting "Knowledge", the rerank model is optional. That's what is written in the Dify's documents.

image

Originally created by @tden-TakahitoUsui on GitHub (Dec 22, 2024). ### Self Checks - [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 (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [X] Please do not modify this template :) and fill in all the required fields. ### Dify version 0.14.1 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce I set the "Knowledge" in Dify "0.14.1". - Index Method: Economical - Retrieval Setting: Inverted Index ### ✔️ Expected Behavior I hope when the workflow use one "Knowledge", the rerank model is optional. ### ❌ Actual Behavior When I use "Knowledge Retrieval" block with this "Knowledge", Dify says "Rerank Model is required". But in this setting "Knowledge", the rerank model is optional. That's what is written in the Dify's documents. - https://docs.dify.ai/guides/knowledge-base/integrate-knowledge-within-application#frequently-asked-questions - https://docs.dify.ai/zh-hans/guides/knowledge-base/integrate-knowledge-within-application#chang-jian-wen-ti ![image](https://github.com/user-attachments/assets/3c7eb15e-e013-4d19-81bc-ab7554fa5fea)
yindo added the 📚 documentationstale labels 2026-02-21 18:20:05 -05:00
yindo closed this issue 2026-02-21 18:20:05 -05:00
yindo commented 2026-02-21 18:20:05 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Dec 22, 2024):

I found a similar closed issue titled Knowledge Retrieval Node Incorrectly Reverts to RerankModel, which was resolved by a pull request. The pull request addressed the issue by ensuring that the top_n parameter is valid and that the query is not empty, improving the user experience with the Wenxin Rerank model [1].

Regarding your current issue, it seems there is a discrepancy between the Dify documentation and the actual implementation in the codebase concerning the 'Knowledge Retrieval' block settings. The documentation suggests that the rerank model should be optional for the 'Economical' index method and 'Inverted Index' retrieval setting, but the implementation requires it. This might indicate a bug or an oversight in the documentation or codebase. Unfortunately, I couldn't find specific information about this discrepancy in the available data.

To continue talking to Dosu, mention @dosu.

Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

@dosubot[bot] commented on GitHub (Dec 22, 2024): <!-- Answer --> I found a similar closed issue titled [Knowledge Retrieval Node Incorrectly Reverts to RerankModel](https://github.com/langgenius/dify/issues/8854), which was resolved by a pull request. The pull request addressed the issue by ensuring that the `top_n` parameter is valid and that the `query` is not empty, improving the user experience with the Wenxin Rerank model <sup>[[1]](https://github.com/langgenius/dify/issues/8854)</sup>. Regarding your current issue, it seems there is a discrepancy between the Dify documentation and the actual implementation in the codebase concerning the 'Knowledge Retrieval' block settings. The documentation suggests that the rerank model should be optional for the 'Economical' index method and 'Inverted Index' retrieval setting, but the implementation requires it. This might indicate a bug or an oversight in the documentation or codebase. Unfortunately, I couldn't find specific information about this discrepancy in the available data. <!-- Dosu Comment Footer --> *To continue talking to [Dosu](https://dosu.dev), mention @dosu.* --- <sup>Help Dosu learn! Give it feedback: [Great Response](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=hallucination) | [Other](https://app.dosu.dev/response-feedback/b46f006e-f2a8-4752-a33d-757012e3b8de?feedback_type=other)</sup>
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 stale 📚 documentation
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#7344
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?