Enable the postgres implementation of text_chunks to support custom fields #2608
+90
−2
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
When storing text_chunks, it is necessary to support the scenario where users' custom chunkers output custom fields. Among the several implementations of KVStorage, only postgres does not support custom fields, while json/mongo/redis natively support custom fields. This commit aims to enable postgres to support custom fields.
Changes Made
custom_datato the LIGHTRAG_DOC_CHUNKS table.Checklist