When I use the knowledge retrieval node and configure two external knowledge bases, the second configured knowledge base will definitely be invoked twice.

langgenius / dify

Dify is an open-source LLM app development platform. Dify's intuitive interface combines AI workflow, RAG pipeline, agent capabilities, model management, observability features and more, letting you quickly go from prototype to production.

Other

49.47k stars 7.08k forks source link

Self Checks

[X] This is only for bug report, if you would like to ask a question, please head to Discussions.
[X] I have searched for existing issues search for existing issues, including closed ones.
[X] I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
[X] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
[X] Please do not modify this template :) and fill in all the required fields.

Dify version

0.10.0

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When I use the knowledge retrieval node and configure two external knowledge bases, the second configured knowledge base will definitely be invoked twice.

DDL: Test.zip

✔️ Expected Behavior

invoked once

❌ Actual Behavior

invoked twice

There isn't specific information available in the Dify documentation or codebase about a known issue where the second configured external knowledge base is invoked twice during a single retrieval process. However, this could potentially be a bug or an unintended behavior in the system.

To address this issue, you might want to:

Check the Configuration: Ensure that the configuration settings for both knowledge bases are correct and consistent. Sometimes, misconfigurations can lead to unexpected behavior.
Review the Code: If you have access to the code, review the logic in the _fetch_dataset_retriever method within the KnowledgeRetrievalNode class. This part of the code is responsible for handling external knowledge bases and might provide insights into why the second knowledge base is being invoked twice ^[1].
Debugging: Add logging or debugging statements in the relevant parts of the code to trace the invocation process and identify where the duplication occurs.
Update or Patch: Ensure that you are using the latest version of Dify, as updates might contain bug fixes related to this issue.

If the problem persists, consider reporting it as a bug in the Dify repository, providing detailed information and any relevant logs or traces to help the maintainers diagnose the issue.

To continue talking to Dosu, mention @dosu.

langgenius / dify