About knowledge of dify #3688

Closed
opened 2026-02-21 18:00:52 -05:00 by yindo · 0 comments
Owner

Originally created by @Yoshitaka-Nishimoto on GitHub (May 25, 2024).

Originally assigned to: @JohnJyong on GitHub.

Self Checks

  • 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).
  • Please do not modify this template :) and fill in all the required fields.

1. Is this request related to a challenge you're experiencing?

Dify's knowlege has the potential to promote the strengthening of its specialized field, but it could not be evaluated because the response process was not understood.

2. Describe the feature you'd like to see

No matter how dify's knowledge structures the data (id splitting) or rearranges it using rerank, I currently don't understand the process, and even just looking at the results, I can't understand it clearly. I'm an engineer, so I'd appreciate it if I could debug and trace the process.

3. How will this feature improve your workflow or experience?

If this function cannot be realized, Dify, although multifunctional,
It has low accuracy and may be considered unusable.

4. Additional context or comments

No response

5. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @Yoshitaka-Nishimoto on GitHub (May 25, 2024). Originally assigned to: @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 submit this report (我已阅读并同意 [Language Policy](https://github.com/langgenius/dify/issues/1542)). - [X] Please do not modify this template :) and fill in all the required fields. ### 1. Is this request related to a challenge you're experiencing? Dify's knowlege has the potential to promote the strengthening of its specialized field, but it could not be evaluated because the response process was not understood. ### 2. Describe the feature you'd like to see No matter how dify's knowledge structures the data (id splitting) or rearranges it using rerank, I currently don't understand the process, and even just looking at the results, I can't understand it clearly. I'm an engineer, so I'd appreciate it if I could debug and trace the process. ### 3. How will this feature improve your workflow or experience? If this function cannot be realized, Dify, although multifunctional, It has low accuracy and may be considered unusable. ### 4. Additional context or comments _No response_ ### 5. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 📚 documentation label 2026-02-21 18:00:52 -05:00
yindo closed this issue 2026-02-21 18:00:52 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify#3688