Documents separator groups for recursive chunking strategy #3848
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kosabogi
added
enhancement
🔍 Preview links for changed docs |
dan-rubinstein
approved these changes
Nov 7, 2025
Member
dan-rubinstein
left a comment
dan-rubinstein
left a comment
There was a problem hiding this comment.
Thanks for adding this documentation. This will really help make it clear what options are available to the user.
benironside
approved these changes
Nov 7, 2025
Contributor
benironside
left a comment
benironside
left a comment
There was a problem hiding this comment.
Nice work. Just a few minor suggestions but nothing blocking.
|
|
||
| ##### Markdown separator group | ||
| You can configure the `recursive` strategy using either: | ||
| - [Predefined separator groups](#separator-groups): [`plaintext`](#plaintext) or [`markdown`](#markdown) |
Contributor
There was a problem hiding this comment.
Suggested change
| - [Predefined separator groups](#separator-groups): [`plaintext`](#plaintext) or [`markdown`](#markdown) | |
| - [Predefined separator groups](#separator-groups): [`Plaintext`](#plaintext) or [`markdown`](#markdown) |
Maybe capitalize to match the following line
Contributor
There was a problem hiding this comment.
or else make "Custom separators" lower case?
| The following example creates an {{infer}} endpoint with the `elasticsearch` service that deploys the ELSER model and configures chunking with the `recursive` strategy using the markdown separator group and a maximum of 200 words per chunk. | ||
| ##### Predefined separator groups [separator-groups] | ||
|
|
||
| Predefined separator groups provide optimized patterns for common text formats: [`plaintext`](#plaintext) for simple line-structured text without markup, and [`markdown`](#markdown) for Markdown-formatted content. |
Contributor
There was a problem hiding this comment.
Suggested change
| Predefined separator groups provide optimized patterns for common text formats: [`plaintext`](#plaintext) for simple line-structured text without markup, and [`markdown`](#markdown) for Markdown-formatted content. | |
| Predefined separator groups provide optimized patterns for common text formats: [`plaintext`](#plaintext) works for simple line-structured text without markup, and [`markdown`](#markdown) works for Markdown-formatted content. |
or maybe "is for"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds documentation for the
plaintextandmarkdownseparator group options available in therecursivechunking strategy.Changes
plaintextandmarkdown)Related issue: #3015