[Feature][RAG] Use PageTextSplitter as the default Splitter for DatasourceKnowledge
lordk911 opened this issue · comments
Search before asking
- I had searched in the issues and found no similar feature requirement.
Description
For DatasourceKnowledge, currently RecursiveCharacterTextSplitter Splitter is the default. This will cause the DDL of a single table to be truncated, resulting in the failure to obtain the correct table structure during RAG, which can be satisfied by using PageTextSplitter.
Use case
No response
Related issues
No response
Feature Priority
Medium
Are you willing to submit PR?
- Yes I am willing to submit a PR!