Open
Description
The latest pgvector version supports sparsevec
.
However, langchain's PGVector supports only one embeddings column in langchain_pg_embedding
table.
It would be great to have a sparse_embedding
column and sparse_embedding
field in PGVector.
I have considered the alternative and that is to have 2 PGVector stores, 1 for dense and 1 for sparse vectors. However there are 2 problems with that:
- PGVector has hardcoded table names for collection and embeddings
- I would like to leverage excellent langchain indexer with SQL manager.