Ensuring original text is preserved in CHUNKING_REGEX #18054
+14
−1
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.
Description
The original default
CHUNKING_REGEX
wasn't preserving the original text, repeating characters in,.;。?!
were reduced to a singe instance, so in a scenario like[text](../path/to/file.md)
this can get reconstructed as[text](./path/to/file.md)
which will not match the original text. This then results inSentenceSplitter.start_char_idx = None
because it fails to find the chunk text in the source document text.Fixes # (issue)
Version Bump?
Type of Change
Please delete options that are not relevant.
How Has This Been Tested?
Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.
Simple Regex Text Preservation Test
Suggested Checklist:
I have made corresponding changes to the documentationI have added Google Colab support for the newly added notebooks.make format; make lint
to appease the lint gods