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

Knowledge: wrong document details report in Parent-Child (full-doc) #8380

New Issue
Closed
opened 2026-02-21 18:25:23 -05:00 by yindo · 5 comments
yindo commented 2026-02-21 18:25:23 -05:00
Owner
Copy Link
Copy Source

Originally created by @DavideDelbianco on GitHub (Feb 18, 2025).

Originally assigned to: @JohnJyong on GitHub.

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.15.3

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Create a nowldgebase using Parent Child mode.
switch from paragraph to full-doc mode and complete the creation of the KB

✔️ Expected Behavior

Because in full-doc, the field we manage is the ChildChunk settings i would expec to see in the document details the chunk size i set for the child and not the parent chunk size

Image

Image

❌ Actual Behavior

Parent chunk size is displayed
Image

Originally created by @DavideDelbianco on GitHub (Feb 18, 2025). Originally assigned to: @JohnJyong on GitHub. ### 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.15.3 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce Create a nowldgebase using Parent Child mode. switch from paragraph to full-doc mode and complete the creation of the KB ### ✔️ Expected Behavior Because in full-doc, the field we manage is the ChildChunk settings i would expec to see in the document details the chunk size i set for the child and not the parent chunk size ![Image](https://github.com/user-attachments/assets/f996bf77-d7a2-43b9-8fa0-40ebe73183b0) ![Image](https://github.com/user-attachments/assets/5d64a952-07aa-4e6a-85d6-a325ded60bd4) ### ❌ Actual Behavior Parent chunk size is displayed ![Image](https://github.com/user-attachments/assets/e07eb411-0c45-4ace-98f4-0782378c1a93)
yindo closed this issue 2026-02-21 18:25:23 -05:00
yindo commented 2026-02-21 18:25:23 -05:00
Author
Owner
Copy Link
Copy Source

@dosubot[bot] commented on GitHub (Feb 18, 2025):

In the Parent-Child knowledge base setup, when using full-doc mode, the parent chunk size is displayed instead of the child chunk size because the entire document is used as the parent chunk and retrieved directly. This approach is ideal for smaller documents where paragraphs are interrelated, requiring full document retrieval. The child chunks are derived from the parent chunk by splitting them based on delimiter rules, but in full-doc mode, the focus is on retrieving the entire document as a single parent chunk for context. Therefore, the parent chunk size is displayed to reflect the full document retrieval approach [1].

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 (Feb 18, 2025): <!-- Answer --> In the Parent-Child knowledge base setup, when using full-doc mode, the parent chunk size is displayed instead of the child chunk size because the entire document is used as the parent chunk and retrieved directly. This approach is ideal for smaller documents where paragraphs are interrelated, requiring full document retrieval. The child chunks are derived from the parent chunk by splitting them based on delimiter rules, but in full-doc mode, the focus is on retrieving the entire document as a single parent chunk for context. Therefore, the parent chunk size is displayed to reflect the full document retrieval approach <sup>[[1]](https://github.com/langgenius/dify-docs/blob/main/en/guides/knowledge-base/create-knowledge-and-upload-documents/2.-choose-a-chunk-mode.md)</sup>. <!-- 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/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=great_response) | [Irrelevant Answer](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=irrelevant_answer) | [Incorrect Sources](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=incorrect_sources) | [Too Verbose](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=hallucination) | [Bug Report](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/014f33fc-775c-45ec-b0fc-35631452d160?feedback_type=other)</sup>
yindo commented 2026-02-21 18:25:24 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Feb 18, 2025):

Afaik, we do not display the child chunk information in the place you displayed.

@crazywoola commented on GitHub (Feb 18, 2025): Afaik, we do not display the child chunk information in the place you displayed.
yindo commented 2026-02-21 18:25:24 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary

  • You reported a bug in Dify version 0.15.3 regarding document details in a knowledge base.
  • The issue occurs in Parent-Child mode when switched to full-doc mode in a self-hosted Docker environment.
  • I clarified that the behavior is intentional, as full-doc mode retrieves the entire document as a single parent chunk.
  • Crazywoola confirmed that child chunk information is not displayed in the location you mentioned.

Next Steps

  • Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here.
  • 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, @DavideDelbianco. I'm [Dosu](https://dosu.dev), and I'm helping the Dify team manage their backlog and am marking this issue as stale. **Issue Summary** - You reported a bug in Dify version 0.15.3 regarding document details in a knowledge base. - The issue occurs in Parent-Child mode when switched to full-doc mode in a self-hosted Docker environment. - I clarified that the behavior is intentional, as full-doc mode retrieves the entire document as a single parent chunk. - Crazywoola confirmed that child chunk information is not displayed in the location you mentioned. **Next Steps** - Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting here. - If there is no further activity, this issue will be automatically closed in 15 days. Thank you for your understanding and contribution!
yindo commented 2026-02-21 18:25:24 -05:00
Author
Owner
Copy Link
Copy Source

@DavideDelbianco commented on GitHub (Mar 23, 2025):

It Is still like that and I think the visualization could be improved, maybe this issue should be changed from big to improvement request

@DavideDelbianco commented on GitHub (Mar 23, 2025): It Is still like that and I think the visualization could be improved, maybe this issue should be changed from big to improvement request
yindo commented 2026-02-21 18:25:24 -05:00
Author
Owner
Copy Link
Copy Source

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

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

Issue Summary:

  • A bug was reported in Dify version 0.15.3 regarding document details displaying parent chunk size instead of child chunk size in full-doc mode.
  • I clarified that this behavior is intentional, as full-doc mode retrieves the entire document as a single parent chunk.
  • Crazywoola confirmed that child chunk information is not displayed in the specified location.
  • You suggested reclassifying the issue as an improvement request for better visualization.

Next Steps:

  • Please confirm 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, the issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!

@dosubot[bot] commented on GitHub (Apr 23, 2025): Hi, @DavideDelbianco. 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:** - A bug was reported in Dify version 0.15.3 regarding document details displaying parent chunk size instead of child chunk size in full-doc mode. - I clarified that this behavior is intentional, as full-doc mode retrieves the entire document as a single parent chunk. - Crazywoola confirmed that child chunk information is not displayed in the specified location. - You suggested reclassifying the issue as an improvement request for better visualization. **Next Steps:** - Please confirm 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, the 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
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#8380
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?