feat: extend postgres vector store with paradedb BM25 support #20024
+7,818
−0
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
This PR introduces ParadeDB vector store integration, extending the PostgreSQL-based store to support BM25 + vector search using ParadeDB.
This implementation is based on llama-index-vector-stores-postgres version 0.5.5, adapted for ParadeDB’s BM25.
This PR:
pg_search
extension.README.md
describing setup, Docker usage, and configuration examples.Fixes
Fixes #
(or leave blank if this is a new feature without a linked issue)
New Package?
llama-index-vector-stores-paradedb
A detailed
README.md
was added with usage examples, setup instructions, and integration notes.The
tool.poetry.dependencies.llama-index-vector-stores-postgres
reference is also declared inpyproject.toml
.Version Bump
0.1.0
Type of Change
How Has This Been Tested?
Suggested Checklist
README.md
)uv run ruff check --fix .
anduv run ruff format .
to appease the lint gods