Feature request: Add ingestion pipeline support to litellm-pgvector
Description
litellm-pgvector currently does not implement the ingestion pipeline.
This prevents users from using PostgreSQL with pgvector as a complete vector datastore, since documents cannot be processed, embedded, and stored through the standard LiteLLM ingestion workflow.
Expected behavior
litellm-pgvector should support the full ingestion pipeline, including:
- Document ingestion and chunking
- Embedding generation
- Vector and metadata storage in PostgreSQL
- Compatibility with the existing retrieval workflow
Why this is important
This is a key missing feature for teams that want to use pgvector as their primary vector datastore. Implementing it would unblock end-to-end ingestion and retrieval workflows without requiring a separate vector database or a custom ingestion implementation.
Related discussion: BerriAI/litellm#30878
Feature request: Add ingestion pipeline support to
litellm-pgvectorDescription
litellm-pgvectorcurrently does not implement the ingestion pipeline.This prevents users from using PostgreSQL with
pgvectoras a complete vector datastore, since documents cannot be processed, embedded, and stored through the standard LiteLLM ingestion workflow.Expected behavior
litellm-pgvectorshould support the full ingestion pipeline, including:Why this is important
This is a key missing feature for teams that want to use
pgvectoras their primary vector datastore. Implementing it would unblock end-to-end ingestion and retrieval workflows without requiring a separate vector database or a custom ingestion implementation.Related discussion: BerriAI/litellm#30878