[PR #14264] [MERGED] feat: add langchain markdown document splitter #46474

Closed
opened 2026-04-29 21:18:19 -05:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/14264
Author: @diwakar-s-maurya
Created: 5/24/2025
Status: Merged
Merged: 7/8/2025
Merged by: @tjbck

Base: devHead: patch-6


📝 Commits (1)

  • 871efb4 feat: add langchain markdown document splitter

📊 Changes

2 files changed (+46 additions, -2 deletions)

View changed files

📝 backend/open_webui/routers/retrieval.py (+45 -2)
📝 src/lib/components/admin/Settings/Documents.svelte (+1 -0)

📄 Description

Pull Request Checklist

  • Target branch: Please verify that the pull request targets the dev branch.
  • Description: Provide a concise description of the changes made in this pull request.
  • Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
  • Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
  • Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
  • Testing: Have you written and run sufficient tests to validate the changes?
  • Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
  • Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
    • BREAKING CHANGE: Significant changes that may affect compatibility
    • build: Changes that affect the build system or external dependencies
    • ci: Changes to our continuous integration processes or workflows
    • chore: Refactor, cleanup, or other non-functional code changes
    • docs: Documentation update or addition
    • feat: Introduces a new feature or enhancement to the codebase
    • fix: Bug fix or error correction
    • i18n: Internationalization or localization changes
    • perf: Performance improvement
    • refactor: Code restructuring for better maintainability, readability, or scalability
    • style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
    • test: Adding missing tests or correcting existing tests
    • WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Markdown format provides data in plain text while still having a way to express hierarchy and formatting. Language models can also understand it well. Using markdown-format-aware document splitting can enahnce RAG.

This PR introduces "Markdown (header)" as new option for "Text Splitter". It uses MarkdownHeaderTextSplitter for its implementation.

Added

  • Add markdown document splitter

Additional Information

It runs RecursiveCharacterTextSplitter again over the splits generated by markdown document splitter. This ensures that final chunks are always of managable size.

Screenshots or Videos

image

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the Contributor License Agreement (CLA), and I am providing my contributions under its terms.


🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/14264 **Author:** [@diwakar-s-maurya](https://github.com/diwakar-s-maurya) **Created:** 5/24/2025 **Status:** ✅ Merged **Merged:** 7/8/2025 **Merged by:** [@tjbck](https://github.com/tjbck) **Base:** `dev` ← **Head:** `patch-6` --- ### 📝 Commits (1) - [`871efb4`](https://github.com/open-webui/open-webui/commit/871efb4ad92f75125152b6296192754cbac6d571) feat: add langchain markdown document splitter ### 📊 Changes **2 files changed** (+46 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `backend/open_webui/routers/retrieval.py` (+45 -2) 📝 `src/lib/components/admin/Settings/Documents.svelte` (+1 -0) </details> ### 📄 Description # Pull Request Checklist - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [x] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description Markdown format provides data in plain text while still having a way to express hierarchy and formatting. Language models can also understand it well. Using markdown-format-aware document splitting can enahnce RAG. This PR introduces "Markdown (header)" as new option for "Text Splitter". It uses [MarkdownHeaderTextSplitter](https://python.langchain.com/docs/how_to/markdown_header_metadata_splitter/) for its implementation. ### Added - Add markdown document splitter --- ### Additional Information It runs RecursiveCharacterTextSplitter again over the splits generated by markdown document splitter. This ensures that final chunks are always of managable size. ### Screenshots or Videos ![image](https://github.com/user-attachments/assets/30bdef10-92a4-439a-a2fe-cee7c629480c) ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [Contributor License Agreement (CLA)](/CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-04-29 21:18:19 -05:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#46474