langgenius/dify
1
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-07-25 13:36:01 -04:00
Code Issues 775 Packages Projects Releases 10 Wiki Activity

Request for API Interface to Update Document Segment Information Without File Upload #6639

New Issue
Closed
opened 2026-02-21 18:16:39 -05:00 by yindo · 2 comments
yindo commented 2026-02-21 18:16:39 -05:00
Owner
Copy Link
Copy Source

Originally created by @yjc980121 on GitHub (Nov 8, 2024).

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

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When using the Dify API to maintain the knowledge base, I need to update the segment information of a file. Through browser inspection, the request interface should be console/api/datasets/{dataset_id}/documents. However, in the existing API documentation, I did not find an equivalent interface.

The closest interface is POST /datasets/{dataset_id}/document/create-by-file, but this interface requires uploading a file. My requirement is to maintain the document segment information through the API without uploading a file.

Suggestion:

I hope Dify can provide an API interface that does not rely on file upload for directly updating the segment information of documents. This would allow for more flexible management and maintenance of the documents in the knowledge base.

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

Originally created by @yjc980121 on GitHub (Nov 8, 2024). ### 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.11.0 ### Cloud or Self Hosted Self Hosted (Docker) ### Steps to reproduce When using the Dify API to maintain the knowledge base, I need to update the segment information of a file. Through browser inspection, the request interface should be console/api/datasets/{dataset_id}/documents. However, in the existing API documentation, I did not find an equivalent interface. The closest interface is POST /datasets/{dataset_id}/document/create-by-file, but this interface requires uploading a file. My requirement is to maintain the document segment information through the API without uploading a file. Suggestion: I hope Dify can provide an API interface that does not rely on file upload for directly updating the segment information of documents. This would allow for more flexible management and maintenance of the documents in the knowledge base. ### ✔️ Expected Behavior _No response_ ### ❌ Actual Behavior _No response_
yindo added the 💪 enhancement label 2026-02-21 18:16:39 -05:00
yindo closed this issue 2026-02-21 18:16:39 -05:00
yindo commented 2026-02-21 18:16:40 -05:00
Author
Owner
Copy Link
Copy Source

@crazywoola commented on GitHub (Nov 8, 2024):

QQ_1731067857330
Navigate to knowledge/api, you will see the docs here. You should not use api starts with services, instead, you should use these apis provided in this doc,

@crazywoola commented on GitHub (Nov 8, 2024): ![QQ_1731067857330](https://github.com/user-attachments/assets/31e82666-d3b7-4bcf-84c5-eadc6783087e) Navigate to knowledge/api, you will see the docs here. You should not use api starts with services, instead, you should use these apis provided in this doc,
yindo commented 2026-02-21 18:16:40 -05:00
Author
Owner
Copy Link
Copy Source

@yjc980121 commented on GitHub (Nov 8, 2024):

QQ_1731067857330 Navigate to knowledge/api, you will see the docs here. You should not use api starts with services, instead, you should use these apis provided in this doc,

I want to re segment instead of update segments, the number of segments will change, modify process_rule

@yjc980121 commented on GitHub (Nov 8, 2024): > ![QQ_1731067857330](https://private-user-images.githubusercontent.com/100913391/384362586-31e82666-d3b7-4bcf-84c5-eadc6783087e.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzEwOTEzMDksIm5iZiI6MTczMTA5MTAwOSwicGF0aCI6Ii8xMDA5MTMzOTEvMzg0MzYyNTg2LTMxZTgyNjY2LWQzYjctNGJjZi04NGM1LWVhZGM2NzgzMDg3ZS5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMTA4JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTEwOFQxODM2NDlaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT00ZGZkY2NmMjQyZjllNzIzZTE0NGVjYmI2N2M1MTVhZDU4Y2ExNDJkNjkxZmU0MjZlNTFjMzg3NzE3NGMxMzgxJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.kpZlK3KphxXoB0pyUyE6-g-BdcbBxudIT3VvxfcHALc) Navigate to knowledge/api, you will see the docs here. You should not use api starts with services, instead, you should use these apis provided in this doc, I want to re segment instead of update segments, the number of segments will change, modify process_rule
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 💪 enhancement
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#6639
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?