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

Dify knowledge retrieval uses a third-party ragflow knowledge base reference section to display only the first file name #12687

New Issue
Closed
opened 2026-02-21 19:08:33 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 19:08:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @xiaozhanxiaozhan on GitHub (Apr 9, 2025).

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

1.1.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Dify knowledge retrieval uses a third-party ragflow knowledge base reference section to display only the first file name

1. Use Dify's own knowledge base：
Image

2. Use the third-party knowledge base RagFlow，only the first file name can be displayed：

Image

Image

I have checked the log of knowledge retrieval node. May the parsing fail because the data format returned by calling RagFlow is inconsistent with Dify's own knowledge base?
the Dify knowledge retrieval node data：

Image
the Dify knowledge retrieval node data returned by calling RagFlow：

Image

✔️ Expected Behavior

Image

❌ Actual Behavior

Only the first file name can be displayed：
Image

Image

Originally created by @xiaozhanxiaozhan on GitHub (Apr 9, 2025). ### 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 1.1.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce **Dify knowledge retrieval uses a third-party ragflow knowledge base reference section to display only the first file name** **1. Use Dify's own knowledge base：** ![Image](https://github.com/user-attachments/assets/42f406f4-3714-4e6b-bc97-de5d8e030050) **2. Use the third-party knowledge base RagFlow，only the first file name can be displayed：** ![Image](https://github.com/user-attachments/assets/03a33cd5-72d3-43a2-bc2f-1f6adb4366e9) ![Image](https://github.com/user-attachments/assets/7950b1ab-1680-4807-b9cf-d0e80374f766) **I have checked the log of knowledge retrieval node. May the parsing fail because the data format returned by calling RagFlow is inconsistent with Dify's own knowledge base?** **the Dify knowledge retrieval node data：** ![Image](https://github.com/user-attachments/assets/74654912-412d-4742-8548-860c17387896) **the Dify knowledge retrieval node data returned by calling RagFlow：** ![Image](https://github.com/user-attachments/assets/1db73839-5203-47dd-b073-fe7480576f39) ### ✔️ Expected Behavior ![Image](https://github.com/user-attachments/assets/42f406f4-3714-4e6b-bc97-de5d8e030050) ### ❌ Actual Behavior Only the first file name can be displayed： ![Image](https://github.com/user-attachments/assets/03a33cd5-72d3-43a2-bc2f-1f6adb4366e9) ![Image](https://github.com/user-attachments/assets/7950b1ab-1680-4807-b9cf-d0e80374f766)
yindo closed this issue 2026-02-21 19:08:33 -05:00
yindo commented 2026-02-21 19:08:34 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Apr 9, 2025):

你好，@xiaozhanxiaozhan！我是一个可以帮助你解决bug、回答问题和成为贡献者的机器人。如果你有任何疑问或需要帮助，欢迎随时问我！我会在这儿等着，直到有人工维护者来回复你。

There are two similar unsolved discussions that might be relevant to your issue:

  1. Do you have the same bug when I use ragflow as a external knowledge - This discussion involves a bug related to using RagFlow as an external knowledge source, which might be similar to the issue you're experiencing with file name display [1].

  2. Why cannot find required text from knowledge base in Dify? - This discussion addresses issues with finding text from the knowledge base, which could be related to the data format inconsistencies you mentioned [2].

These discussions might provide insights or potential solutions to your problem.

To continue talking to Dosu, mention @dosu.

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

@dosubot[bot] commented on GitHub (Apr 9, 2025): <!-- Greeting --> 你好，@xiaozhanxiaozhan！我是一个可以帮助你解决bug、回答问题和成为贡献者的机器人。如果你有任何疑问或需要帮助，欢迎随时问我！我会在这儿等着，直到有人工维护者来回复你。 <!-- Answer --> There are two similar unsolved discussions that might be relevant to your issue: 1. [Do you have the same bug when I use ragflow as a external knowledge](https://github.com/langgenius/dify/discussions/15854) - This discussion involves a bug related to using RagFlow as an external knowledge source, which might be similar to the issue you're experiencing with file name display <sup>[[1]](https://github.com/langgenius/dify/discussions/15854)</sup>. 2. [Why cannot find required text from knowledge base in Dify?](https://github.com/langgenius/dify/discussions/10459) - This discussion addresses issues with finding text from the knowledge base, which could be related to the data format inconsistencies you mentioned <sup>[[2]](https://github.com/langgenius/dify/discussions/10459)</sup>. These discussions might provide insights or potential solutions to your problem. <!-- 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/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/fb2723aa-dd70-4bf2-9e6e-a280a76eda69?feedback_type=other)</sup>
yindo commented 2026-02-21 19:08:34 -05:00
Author
Owner
Copy Link
Copy Source

@briqt commented on GitHub (Apr 10, 2025):

You can refer to the PR.：https://github.com/langgenius/dify/pull/17843

@briqt commented on GitHub (Apr 10, 2025): You can refer to the PR.：https://github.com/langgenius/dify/pull/17843
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
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#12687
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?