Fix: Correct Markdown chunk positioning (#12686) #12729
Open
+360
−359
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
dosubot
bot
added
the
size:XL
Magicbook1108
added
ci
dosubot
bot
added
the
size:XL
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What problem does this PR solve?
Fix: Correct Markdown chunk positioning (#12686)
Markdown chunking now aligns with the DOCX merge behavior introduced in #12455. Content is produced as ordered (text, image, table) tuples and passed through the downstream chunking pipeline with positional information preserved end-to-end.
As a temporary measure, the overlapped parameter is disabled while the context window size is enabled to maintain continuity without compromising offset accuracy.
Fix: DOCX ingestion pipeline return type error
Fix: Markdown ingestion pipeline return type error
Refactor: Rename shared functions to reflect usage across both DOCX and Markdown pipelines
Type of change