-
Notifications
You must be signed in to change notification settings - Fork 9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation Recognition Fails When Using create_by_text in Parent-Child Mode in the Knowledge Base API #13007
Comments
The issue you're experiencing with the 'create_by_text' API endpoint in parent-child mode seems to be related to the segmentation settings not being applied correctly. Here are a few things to consider:
If the problem persists, consider reviewing the API documentation for any updates or known issues related to segmentation settings. Additionally, ensure that your Dify version is up to date, as newer versions might contain fixes for such issues. To continue talking to Dosu, mention @dosu. Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other |
Please upgrade to v0.15.2. |
@crazywoola Hi crazywoola, I have upgraded Docker Compose to the latest version, but the result remains the same; the segment configuration does not take effect.
|
Self Checks
Dify version
v0.15.1
Cloud or Self Hosted
Self Hosted (Docker)
Steps to reproduce
Step 1:
Execute the following curl command:
The response is as follows:
Step 2: The knowledge base shows that the document has been loaded successfully, but the "Preview Segmentation Interface" displays no content.
Step 3: Upon clicking on the segmentation settings, it's observed that the parent-child mode is correctly set. However, the delimiters and corresponding segment lengths are not properly configured (they remain at default settings, such as the delimiter being \n\n and the parent segment length being 500).
After manually setting these parameters, the segmentation works correctly, and the preview displays as expected.
✔️ Expected Behavior
No response
❌ Actual Behavior
No response
The text was updated successfully, but these errors were encountered: