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

Document api missing also the metadata missing for the reuslt of knowledge retrieval #8424

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

Originally created by @hjnnewton on GitHub (Feb 19, 2025).

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

1. Is this request related to a challenge you're experiencing? Tell me about your story.

I was trying to use chatflow to return the key field in metadata for documents returned by knowledge retrieval block. The returned segments can't let me to redirect the source document, since there is no api for getting document details.
I read the apis for knowledge management and found the just api by providing dataset and document id to get the document detail is missing, i am curious about the concerns. The document list api doesn't return the metadata neither.
I would need to contain some metadata for the document such as the file url, etc to help improve the output, but it seems to be not supported.

2. Additional context or comments

No response

3. Can you help us with this feature?

  • I am interested in contributing to this feature.
Originally created by @hjnnewton on GitHub (Feb 19, 2025). ### 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] [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:） - [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? Tell me about your story. I was trying to use chatflow to return the key field in metadata for documents returned by knowledge retrieval block. The returned segments can't let me to redirect the source document, since there is no api for getting document details. I read the apis for knowledge management and found the just api by providing dataset and document id to get the document detail is missing, i am curious about the concerns. The document list api doesn't return the metadata neither. I would need to contain some metadata for the document such as the file url, etc to help improve the output, but it seems to be not supported. ### 2. Additional context or comments _No response_ ### 3. Can you help us with this feature? - [ ] I am interested in contributing to this feature.
yindo added the 🐞 bug label 2026-02-21 18:25:38 -05:00
yindo closed this issue 2026-02-21 18:25:38 -05:00
yindo commented 2026-02-21 18:25:38 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Mar 22, 2025):

Hi, @hjnnewton. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

  • You reported a problem with the chatflow feature in the knowledge retrieval block.
  • Specifically, there is a lack of an API to access key metadata fields like file URLs for documents.
  • The existing document list API does not provide the required metadata.
  • This limitation affects your ability to enhance output by linking to source documents.
  • No further activity or comments have been made on the issue.

Next Steps

  • Please let us know if this issue is still relevant to the latest version of the Dify repository by commenting on this issue.
  • If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Mar 22, 2025): Hi, @hjnnewton. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog. I'm marking this issue as stale. **Issue Summary** - You reported a problem with the chatflow feature in the knowledge retrieval block. - Specifically, there is a lack of an API to access key metadata fields like file URLs for documents. - The existing document list API does not provide the required metadata. - This limitation affects your ability to enhance output by linking to source documents. - No further activity or comments have been made on the issue. **Next Steps** - Please let us know if this issue is still relevant to the latest version of the Dify repository by commenting on this issue. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
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 🐞 bug
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#8424
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?